Seems pretty well defined here: https://developers.google.com/appengine/docs/java/channel/overview#Caveats
"One Client Per Client ID Only one client at a time can connect to a channel using a given Client ID, so an application cannot use a Client ID for fan-out. In other words, it's not possible to create a central Client ID for connections to multiple clients (For example, you can't create a Client ID for something like a "global-high-scores" channel and use it to broadcast to multiple game clients.)" On Tuesday, October 9, 2012 3:41:21 PM UTC+2, gops wrote: > > its undefined behavior. they never said it will not work or prohibited. > they said undefined. > > On Tue, Oct 9, 2012 at 1:54 AM, Richard Watson > <[email protected]<javascript:> > > wrote: > >> I'm sure it's very unlikely to work reliably. If you need that, until >> Google makes a policy change I'd suggest using something like Pusher. >> http://pusher.com/ >> >> >> On Monday, October 8, 2012 7:17:10 PM UTC+2, Andrew Mackenzie wrote: >>> >>> This overview page for the Channel API >>> >>> https://developers.google.com/**appengine/docs/java/channel/**overview<https://developers.google.com/appengine/docs/java/channel/overview> >>> >>> states in the "Caveats" section: >>> >>> "Only one client at a time can connect to a channel using a given >>> Client ID, so an application cannot use a Client ID for fan-out. In other >>> words, it's not possible to create a central Client ID for connections to >>> multiple clients (For example, you can't create a Client ID for something >>> like a "global-high-scores" channel and use it to broadcast to multiple >>> game clients.)" >>> >>> I can confirm that you CAN have multiple clients listen on the same >>> channel (via the same Channel ID) and that it works, a single message sent >>> on the channel is received by all listening clients. >>> >>> Can anyone from google comment? >>> - is the documentation out of date and the design and implementation do >>> support this >>> - am I "just lucky" and this could break any time....and I should be >>> planning a redesign >>> >>> It seems a very useful design feature of channels when pushing out >>> status updates to multiplayer games, group chats and many other use cases. >>> >>> I have tried having one page (GWT app) listen on more than one channel, >>> and as stated in the Caveats, it seems to NOT work. >>> As David Bowie would say: "If I say I can't do it, I can't do it, I >>> don't make false claims" :-) >>> >>> Thanks. >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/BF7hA1CZZiIJ. >> >> To post to this group, send email to >> [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/01UpUw7zSwIJ. 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.
