On 11 Кві, 09:33, Robert Kluin <[email protected]> wrote: > As I recall, messages sent to a channel who's client is disconnected are > silently dropped. Adding presence to the Channel API is on the roadmap. > http://code.google.com/appengine/docs/roadmap.html
Oh... too bad. Even with presence it will make just little bit easier to use Channel API for client's updates... Problem is limit of 8k channels, and as for now we need to _recreate_ a new channel each time client connects to server (even with same client-id) if it do not have a token... So if user press refresh button, and we did not saved token at client side (cookie or html5 client storage), a new channel is opened. It is so easy to get to 8k limit even with less then 8k users. I think the best use-case of Channel API is to make possibility to develop rich web applications (with possible offline support) that can be updated by server's events about something was changed. Do do that we need publish-subscribe API with offline queue. I hope sometime it will be a possibility to implement it on GAE with less efforts then it is needed now. So, waiting for (some kind of wishlist about Channel API): 1. Presence notifications 2. Re-opening channels for same clients (or sliding expiration for tokens) 3. (ideal) offline messages for clients, that was not connected while sending message -- 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.
