MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you:
By Rania Hadi, MENA Outreach Manager

View this post in Arabic

Last May, I joined the MENA Outreach team and was swiftly transported to Rabat for my first event (as an organizer) in Morocco. it is hard to believe that a year has passed, but here we are again, preparing for our upcoming g|maroc event!

Our first g|day of 2012 was in Jeddah, and we had a great time learning from, and interacting with, the vibrant tech and business communities - and I even got to exercise my Arabic skills on stage. We hope the fun and energy continues at g|maroc 2012, to be held in the city of Mohammedia, on June 7-8. We chose this location to be between Casablanca and Rabat, but we look forward to having many people attend from all around Morocco.

I’m looking forward to a few things: interacting with participants, testing my French and Arabic skills (fingers crossed), and especially, the new and updated sessions. Based on participant feedback from our previous events, we’re changing the content and format this time to make sure we cover topics that are useful for advanced users. We’ll also have Google engineers, product managers, and business leaders available to answer any questions.

g|maroc isn’t just about us, though; we also want to showcase Moroccan talent! If you have created or built something cool using a Google product, technology, or tool, be sure to tell us about it while registering. You may get the chance to present at g|maroc, so be detailed and show us what you’ve got.

Registration opens today, and it’s free. So register now, tell your friends about it, and let us know what you want to see at the event. Morocco was a fantastic first start for me, and I hope the tradition continues!


Rania Hadi has been with Google since 2004 and now works on Outreach in the Middle East & North Africa. She focuses on building relationships and promoting Google technologies with the developer and tech communities.

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master

Seo Master present to you: By Dion Almaer, Google Developer Programs

Bob Lee is a Software Engineer at Google, currently leading up the charge on the core Android APIs. He is also one of the founders of the Google Guice project, and was the interviewee on the very first Google Developer Podcast on the topic.

He also just created a little fun application called Twubble that helps you find potential friends and followers on Twitter. The Twitterati are all over this application, and Biz Stone of Twitter even attributed it as one of a handful of reasons that have driven the rise in followers recently.

This is Bob's first GWT application, so I wanted to sit down and talk to him about why he built the application, his experience with GWT, how he integrated with Twitter, and any other nuggets of information that I could get out of him.

Please, listen in to our conversation, and let us know if you have any questions in the comments:

2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

أسطول نابليون 1865

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة

Seo Master present to you: I set a quarterly goal to write an application in my 20% time that uses publicly available Google APIs. While some would call this scenario testing, I refer to it as "method user experience design" (think method acting). The process can often be painful, but I do it in the hope that it will make me a better designer. It puts me in the shoes of our customers who build products on top of Google's products. I read the same documentation, search the web for the same solutions, write code against the same APIs, and deploy to the same infrastructure. From this exercise come product improvements and empathy. I also enjoy attempting to make something useful, sketching with Python and JavaScript (the charcoal and conte crayon of web development), and proving that 20% time is alive and well.

When it came time to pick last quarter's application, I wanted to work with YouTube's APIs for two reasons: I have a background in video (as a filmmaker and as a software designer) and I wanted to share family videos with my oldest brother, who is hard of hearing and learning disabled. Fast forward a few months later and I had CaptionTube, an application for creating captions for YouTube videos. CaptionTube has launched on TestTube and Hiroto has written a post about it on the YouTube blog.

In addition to the YouTube Data and Player APIs, the application is hosted on Google App Engine and uses the Datastore, Google Accounts, Mail, and URLFetch Python APIs. I used several open source software projects to create it: Django and jQuery, and app-engine-patch. If you are attending Google I/O in May and would like to ask me questions about my experience or discuss your experience using Google's developer's products, please look for me in the developer sandbox or office hour sessions.

By John Skidgel, App Engine Team2013, By: Seo Master

Seo Master present to you:

Bryan

Matthew

By Matthew Steele and Bryan McQuade,
PageSpeed Insights Team

At Google, we strive to make the whole web fast. Our work in this area includes PageSpeed, Google Chrome, and the SPDY protocol, among other efforts. In December of 2011, to make it easy for you to enable the SPDY (pronounced "SPeeDY") protocol on your sites, we released an early beta of mod_spdy, an Apache module that adds SPDY support to the Apache HTTPD server. We’ve spent the last few months working with our early adopters to fix bugs and tune performance of the module. Today, we’re launching a version of mod_spdy that we encourage you to try on your web server.

Installing mod_spdy

To install mod_spdy on your Apache 2.2 server, simply download the appropriate mod_spdy Debian or RPM package for your platform, or compile from source. Once installed, your Apache server will begin using SPDY to communicate with SPDY-compatible browsers (e.g. Google Chrome, Android, and recent versions of Firefox). SPDY runs over HTTPS, so any HTTP (non-HTTPS) traffic on your site will not be affected by mod_spdy. Further, since SPDY requires server-side support for the NPN TLS HTTPS extension, which is not available in most current Apache environments, a version of mod_ssl with NPN support is included with the mod_spdy packages.

Enabling SPDY for your site improves performance in several ways:

• The server and browser can compress HTTP headers, saving bytes on the network.
• Multiple resource requests can be multiplexed over a single TCP connection, saving connections on the network.
• The browser can request all page resources at once instead of a few at a time, which reduces the number of network round-trips needed between server and client.

We've tested mod_spdy using locally-mirrored pages from popular websites, and have seen significant speedups compared to serving via plain HTTPS – comparable to the gains that Google’s own servers achieve by using SPDY – with no extra configuration and negligible effect on Apache’s CPU and memory usage. In extreme cases, for example, pages with many small resources, we’ve seen mod_spdy reduce load times by more than 50%.



How mod_spdy works in Apache

Implementing SPDY in Apache posed several interesting challenges. For example, multiplexing is an important performance feature of SPDY which allows for multiple requests in a single SPDY session to be processed concurrently, and their responses interleaved down the wire. However, due to the serialized nature of the HTTP/1.1 protocol, the Apache HTTP server provides a one-request-per-connection architecture. Apache’s connection and request processing normally happens in a single thread, like so:


This works well for HTTP, but it presents a problem for multiplexed protocols like SPDY because in this flow, each connection can only process one request at a time. Once Apache starts processing a request, control is transferred to the request handler and does not return to the connection handler until the request is complete.

To allow for SPDY multiplexing, mod_spdy separates connection processing and request processing into different threads. The connection thread is responsible for decoding SPDY frames and dispatching new SPDY requests to the mod_spdy request thread pool. Each request thread can process a different HTTP request concurrently. The diagram below shows the high-level architecture.


Happily, all this is almost completely invisible to users and server administrators alike--you can continue to use your existing Apache modules and configurations.

Download mod_spdy for your platform and give it a try, and let us know what you think on our mailing list. mod_spdy is an open-source project and we welcome contributions. We are continuing to add new features, tune performance, and improve support for up-and-coming versions of the SPDY protocol.


Matthew Steele and Bryan McQuade are Software Engineers on the Google PageSpeed Insights Team in Cambridge, MA. When not working on mod_spdy, they focus on developing tools to help site owners understand how to speed up their sites.

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you: 2013, By: Seo Master