In practice, when creating a web application that works with GData, one generally has to create a GData proxy servlet for the application. This introduces latency because now a request to Google requires an "extra hop" to go through the web application's server, as well as a bunch of computation to sign the feed URL requested by the server.
Is there support for GData in the CORS/XMLHttpRequest Level 2/postMessage family of messaging technologies? Ideally, the web application would be able to send the user's OAuth token down to the browser, and the client could use that OAuth token (without the consumer secret of the web application) to make GData requests directly to Google. This would be comparable to how Google's web applications work, where the client makes a direct request to the server, supplying only a cookie for authentication. Eliminating the need for a proxy would considerably cut down the bandwidth costs for the server component of the web application (without increasing the amount of traffic to Google), and would improve the responsiveness of the web application. -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://code.google.com/apis/calendar/community/forum.html
