Slightly OT but the roadmap could sure do with an update. A couple of those "Features on Deck" are already in the current SDK.
On 4 February 2011 07:55, Ikai Lan (Google) <[email protected]> wrote: > In general, we don't make comments on upcoming features. You are welcome to > check the roadmap for updates: > http://code.google.com/appengine/docs/roadmap.html > While we're planning Channel API improvements, have you looked into > providers such as beaconpush.com or pubnub.com? If there's a product you are > looking to build, you should take a pragmatic approach and look into what'll > work instead of being blocked waiting on features that need to be > implemented. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger: http://googleappengine.blogspot.com > Reddit: http://www.reddit.com/r/appengine > Twitter: http://twitter.com/app_engine > > > On Thu, Feb 3, 2011 at 10:36 AM, Peter Petrov <[email protected]> wrote: >> >> Today there was a GAE SDK 1.4.2 prerelease. I was quite disappointed that >> it had no Channel API related updates/improvements in the release notes. >> Since there is also no official roadmap announced for the Channel API, can >> we get some unofficial update about the features and improvements coming in >> the near/distant future? >> >> Here is a short wishlist from me: >> >> 1. Batch send method (efficiently fan-out one message to a potentially >> large number of channels). Moishe said this was planned some time ago. >> >> 2. Channel presence (connect/disconnect notifications to the application). >> This is also being worked on according to Moishe. >> >> 3. Charge CPU on channel disconnect time, instead of token creation time. >> This would allow us to pay for the actual usage, instead of the current >> fixed 2-hour tokens, which require us to implement complex and imperfect >> token reuse schemes. Hopefully this shouldn't be too hard to implement given >> that you are already working on disconnect notifications. >> >> 4. Direct access to the lower Channel API layers for non-browser based >> clients, bypassing the JavaScript long-polling Comet layer. E.g. something >> like allowing a client to connect via XMPP to [email protected] >> using the channel_token as password. >> >> Any status updates regarding these or other planned improvements would be >> appreciated. Thanks! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" 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://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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://groups.google.com/group/google-appengine?hl=en.
