The AJAX Libraries API is a content distribution network and loading architecture for the most popular open source JavaScript libraries. By using the Google AJAX API Loader’s
google.load()method, your application has high speed, globaly available access to a growing list of the most popular JavaScript open source libraries
Tag Archive for 'google'
A few days ago I wrote about how to configure Wordpress to use Google’s cache proxy servers to serve images. After writing that entry I kept thinking to myself that there had to be a better/easier way to accomplish this other than changing Wordpress settings. Well I finally figured it out and got it working on my other blog DavidChiu.net. It involves using mod_rewrite and symbolic links. First you need to create a symbolic link to the Wordpress /uploads/ folder. For example:
ln -s wp-content/uploads/ images/cache
Then you just need to modify your .htaccess file:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^.*wp-content/uploads(.*) http://gmodules.com/ig/proxy?url=http://davidchiu.net/images/cache$1 [R,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
And voila! All images will now be served by Google’s proxy cache!
Websites that are not social networks may still want to be social — and now they can be, easily. With Google Friend Connect (see http://www.google.com/friendconnect following this evening’s Campfire One), any website owner can add a snippet of code to his or her site and get social features up and running immediately without programming — picking and choosing from built-in functionality like user registration, invitations, members gallery, message posting, and reviews, as well as third-party applications built by the OpenSocial developer community.
Visitors to any site using Google Friend Connect will be able to see, invite, and interact with new friends, or, using secure authorization APIs, with existing friends from social sites on the web, including Facebook, Google Talk, hi5, orkut, Plaxo, and more.
Here’s another technology I need to start looking into: OAuth. ProgrammableWeb describes it as:
Like the feature on many cars today where you give the parking attendant a special key to your car that gives him some, but not all, access to your vehicle. On the Web you now have your own keys to dozens of sites but how to best handle the mashup-style case of site A wants you to grant them access to get some data from site B? Ideally you don’t want to give site A your password to site B. OAuth aims to simplify this problem: “It allows you the User to grant access to your private resources on one site (which is called the Service Provider), to another site (called Consumer, not to be confused with you, the User).”
Google has stated that they are going to use this technology for all their API’s.
I’ve spent a lot of time thinking about CDNs (content delivery networks) because of the challenges I’ve been dealing with user submitted photos on a highly trafficked site. Most projects I work on use Akamai with great success, but what about alternatives CDNs for personal projects? What first came to mind was Flickr. I mean why not? Flickr was built to serve photos so why couldn’t Flickr serve as a CDN for images on my site? The next thought that came to mind was Google. Google already caches websites and images, so why not use Google as a CDN? So I did a quick search and found a tutorial of how to write a Google Gadget that will cache images. Sounds perfect! Has anyone implemented this across their site? What are the caveats?
I also found this interesting P2P cache/CDN called Coral that is worth looking into.