Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Seo Master present to you: By Christine Songco, Google Developer Programs

Google Code has highlighted many developers who've created applications using AppEngine, OpenSocial, AdSense, and Google Maps, however, we often forget to reflect on the stories of the people behind the code. In a series of upcoming blog posts we're calling Google Narratives, we'll be telling these stories to allow our developer community to interact and inspire each other to create or even improve existing projects. At last year's Google I/O, we met Dan Shahin of Hijinx Comics, whose creativity in using open source projects to build his business really makes him stand out. Dan agreed to chat with us and share his story. Thanks, Dan!

The story of Dan and how he came to own a comic book store.

At 28 years running, Hijinx Comics, is the oldest comic book store in San Jose, California. From both a personal and business perspective, Hijinx Comics holds a special place in Dan Shahin's life. At the early age of 11, Dan was hired at Hijinx, which was at the same location at the time but went by a different name. Dan continued to work there throughout high school, building his lifelong passion for comics. He left the comic store behind to attend college and later worked at a number of high tech jobs, gaining experience in UNIX systems administration, release management, and software engineering. But by the year 2000, still Dan couldn't shake the feeling that something was missing in his life. Hours of soul-searching revealed that the missing piece was the excitement and passion that he had once experienced when working with comics.

Dan decided to get in touch with the owner of the comic book store. It turned out to be perfect timing because the owner of the store was ready to sell. Dan picked up everything he owned and moved back to his old neighborhood to run the comic book store. He reopened the store as Hijinx Comics and expanded on the traditional business of collectible comics and novelty items with a new focus on graphic novels and books focused on entertainment reading.

Because of the amount of time Dan had worked with comics as a teenager, he had keen awareness of the pain points related to subscriptions and inventory. Drawing on these experiences, he developed a software suite to manage the subscriptions and inventory of his shop and of a brand new online bookstore. Best of all, he opensourced the whole offering to help other comic book stores alleviate the same issues. From there, a side business grew that involved him consulting and implementing a management system and hosting solution to other comic book stores across the nation.

Today, Dan's working on Ver.2 of his project while Ver.1 runs his current business needs. Below are some excerpts from our meeting with Dan.

Q: Tell me about your Google implementation and if there were any obstacles.

A:
I use a lot of Google Code products to build my own open source comic shop management system. I use Google Checkout for my online bookstore ( http://www.comicbookshelf.com ) and did the level 2 integration myself in my custom LAMP application. I also make heavy use of Google Analytics [used to compare data from his own raw server logs], Charts API, Apps for Domains and thanks to last year's I/O, I'm getting into App Engine development as well as Gears, which is what really brought me to Google I/O. My web-based point of sale system uses all of the Gears APIs to bring down UI latency and to allow offline use, which are the two greatest sticking points to current adoption of similar systems. The documentation is well-written with one exception. It would be nice to have a cookbook section - that type is more helpful. More real-life examples in more detail, casual, reader friendly and a commonly used code section. They tend to have lots of detail and the high level can sometimes be fuzzy


Q: What effect have you seen with your customers as a result of the Google implementation?

A: Customers usually come to visit the store but can also log in and update their subscriptions on their own. There's a quicker checkout process since they do the rest of their browsing online. We have a book club where we collect email addresses for customers that buy certain novels online. Customers are also able to offer reviews or books we sell. These reviews are available both online and in the store. We keep track of this type of data in a CRM and based on it, can help recommend favorites and offer Netflix type suggestions.
We're excited to kick off the Google Narratives Series and plan to highlight more developers in our community so if you have a story like Dan's that you'd like to share with us, we're accepting submissions via our online submission form. Better yet, come tell us your story at Google I/O!

2013, By: Seo Master
مشاركة :
خلفيات وصور رائعة hd wallpapers






خلفيات وصور رائعة hd wallpapers
المصدر: المصفوفة
Seo Master present to you: At Google we’re constantly trying to make the web faster — not just our corner of it, but the whole thing. Over the past few days we’ve been rolling out a new and improved version of show_ads.js, the piece of JavaScript used by more than two million publishers to put AdSense advertisements on their web pages. The new show_ads is small and fast, built so that your browser can turn its attention back to its main task — working on the rest of the web page — as soon as possible. This change is now making billions of web pages every day load faster by half a second or more.

The old show_ads did lots of work: loading additional scripts, gathering information about the web page it was running on, and building the ad request to send back to Google. The new show_ads has a different job. It creates a friendly (same-origin) iframe on the web page, and starts the old script with a new name, show_ads_impl, running inside that iframe. The _impl does all the heavy lifting, and in the end the ads look exactly the same. But there’s a substantial speed advantage: many things happening inside an iframe don’t block the web browser’s other work.

How much of an effect this has depends on context: a page with nothing but ads on it isn’t going to get any faster. But on the real-world sites we tested, the latency overhead from our ads is basically gone. Page load times with the new asynchronous AdSense implementation are statistically indistinguishable from load times for the same pages with no ads at all.

The new show_ads is a drop-in replacement for the old one: web site owners don’t need to do anything to get this speed-up. But these dynamically-populated friendly iframes are finicky beasts. For now, we’re only using this technique on Chrome, Firefox, and Internet Explorer 8, with more to come once we’re sure that it plays well with other browsers.

And what if you’ve built a page that loads AdSense ads and then manipulates them in exotic ways not compatible with friendly iframes? (This is the web, after all, land of “What do you mean that’s ‘not supported’? I tried it, and it worked!”) You can set “google_enable_async = false” for any individual ad slot to revert to the old blocking behavior. But if your site loads ads in some tortuous way because you were looking for latency benefits, consider giving the straightforward invocation of show_ads.js a whirl. Because now, we’re fast.

2013, By: Seo Master
Powered by Blogger.