+1 for the channel presence. This is not really a feature, rather a lack of "basic" functionality (in my opinion).
On Feb 3, 7:36 pm, Peter Petrov <onest...@gmail.com> wrote: > Today there was a GAE SDK 1.4.2 > prerelease<http://code.google.com/p/googleappengine/downloads/list>. > 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 channel...@appspotchannel.com > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
