Add platform, for RPC (root request — request that a user is created and not a person and prompting the user to provide a user name) or for shared files (requesting two or more files to be shared) — these behaviours are identified by CAPRA as UDP protocol delivery, for contextual data.
However, in the current version of Google App Engine, there was a mode where UDP mappings are not supported. This caused some problems with a rewrite of the app’s webforms and shared documents, because they cannot be efficiently transformed into UDP messages.
« Google App Engeneering API, September 3, 2009 (includes tips from CAPR, as summarized by Roger Rowland).
Google App Engine offers a dynamic web-viewer for apps, but this does not feature forwarding support. Google approaches this problem by automatically forwarding UDP packets with the callback function. This extension supports 100% functionality, and it is controlled by using GET/POST proxies to the incoming UDP response. The goal of this extension is to enable the web viewer to retrieve the UDP source address of the viewer and then forward the UPDATE requests as well. UDP is currently the default standard for forwarding web-data to the website.
Goes.beta, March 2010, Google Appengine deployment.
17-February 2011, Google made extensive changes to the Google Application Framework to achieve a full forwarding API.
04-April 2011, The Google App engineer is also available for talk.
09-August 2011, Forum posts discussing Google App App Engine UDP support.
22-Apr-2012, Google updated the Google Play Tools utility to support UDP IPv6.
08-September 2012, Google released The Unconnected API, a deep fuzzing tool for the App Engine.
01-Nov-2014, Google launched several streamlined production tools: open-sourced, published, and owned by the company.
31-Spr-2015, Google changed the following URL API to: http://get.google.com/p/gobo/project/ker