OAuth Playground. Important: OAuth 1.0 was officially deprecated on April 20, 2012, and is no longer supported. We encourage you to migrate to OAuth 2.0 as soon as possible. OAuth documentation This document describes how to get started using Google's implementation of the OAuth protocol to authorize a web application's requests for access to a user's data. If instead your application is installed on a computer or a mobile device, you should read the documentation on OAuth for Installed Apps. Prerequisites This document is written for web application developers using the Google Data APIs to access a user's data. OAuth 1.0 for Google accounts is going away.
Schedule for user-visible changes to the approval page: The OAuth authorization process The OAuth authorization process involves a series of interactions between your web application, Google's authorization servers, and the end user. At a basic level, the process is as follows: If the user is not already logged in, Google prompts the user to log in. Code Playground. Bring Your Own Data: Google Opens Up Visualization API. When Google launched its Visualization API in March, it only allowed developers to create applications on top of spreadsheets in Google Docs. Starting today, developers can also use the API to create graphs and gadgets from any data source connected to the web, including SQL databases and Excel spreadsheets.
The Visualization API gives developers the ability to build gadgets, using a set of over 40 different types of visualizations, ranging from interactive bar charts and timelines, to maps and gauges. According to Itai Raz from the Visualization API team, Google also created and documented an open-source Python library that will allow developers to start using the API quickly and which runs on Google's AppEngine. Salesforce Today, Salesforce.com also announced that it has created a number of tools that will make using the Visualization API easier for Salesforce's own customers and developers. Reporting in the Cloud. Learning AJAX APIs Made Easier: Google Releases API Playground. Code Playground. Letting Google Load jQuery… The Right Way | CoryMathews.com. For some time now I have been letting google load the jQuery and jQuery UI libraries for me. There are many benefits to it which I will not get into, you can read more reasons to use it elsewhere.
However I did notice something worth posting. You may be loading the jQuery library like so: Well if you are then you are doing it wrong. It was ySlow that told me why. Try changing that one line to the following and take another look at ySlow. Notice the difference? For those of us that are to lazy to try it out here is the result with the googleapis.com loaded instead of the googlecode.com.
You can see instead of downloading 57.2kb that you would with the googlecode file the gzip compression brings it down to 19kb. The same rule would apply for other libraries that are hosted by google. such as mootools, or even the jQuery UI. So next time you go to include the library make sure to do it the right way. Now I just need to switch all the sites I have that are using it.. such as this one. Libraries API - Developer's Guide - Google Libraries API - Google Code.
3 reasons why you should let Google host jQuery for you - Encosia. All too often, I find code similar to this when inspecting the source for public websites that use jQuery: If you’re doing this on a public facing website, you are doing it wrong. Instead, I urge you to use the Google Hosted Libraries content delivery network to serve jQuery to your users directly from Google’s network of datacenters.
Doing so has several advantages over hosting jQuery on your server(s): decreased latency, increased parallelism, and better caching. In this post, I will expand upon those three benefits of Google’s CDN and show you a couple examples of how you can make use of the service. Just here for the links? If you’ve already read this post and are just here for the links, you’re in the right place! If you care about older browsers, primarily versions of IE prior to IE9, this is the most widely compatible jQuery version: jQuery 1.x (OldIE support) If you don’t care about oldIE, this one is smaller and faster: jQuery 2.x (smaller, faster, and no OldIE support) Better caching.