Tim, after a first glimpse on the newly published channel doc - still wet - it looks like:
o only one client is allowed per cannel id o no clean-up is needed o connected clients must be tracked by the server If you plan to create an entity per active channel in the datastore - this could be a child of the user's entity if you keep an entity per user in the datastore - you could use the string representation of this entity's key as the channel id, which guarantees uniqueness and avoids implementing a mechanism for id creation. I won't go into details about the fancy footwork that is needed to keep track of the client's connection status... BTW, in the updated admin console the (daily) quota of "Channels Created" is given as 1,007,640 (imho fair enough), "Channel Data Sent" as 2,088.13 GBytes, which should all be achieved in no more than 91,995,495 API calls (and the price of "Always On" is 0.30$ per day) Cheers, R. -- 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.
