Albert, Berry, Mike and Mars, There are several broadcasting services available today. Twitter Scale Services like http://www.pubnub.com for mobile apps, websites and tablet apps are easy to use. Others like Pushser and Beacon are great and have their own applications. I like PubNub because it has a free branded option http://www.pubnub.com/price in their hosting plans.
Stephen On May 3, 12:08 pm, Mars <[email protected]> wrote: > Hate to advertise for someone else here, but I've been > usinghttp://beaconpush.combecause of the lack of broadcast support in GAE. > I also noted that each Channel setup consumes 2s CPU (not sure if it's > still the case), which is simply not acceptable for my app. > > Cheers, > > Mars > > On May 3, 7:01 am, Mike Wesner <[email protected]> wrote: > > > > > > > > > I think it will work for a few (~8) connections, but then the next one > > you connect will sort of disconnect one of the others. > > > On May 3, 7:44 am, Barry Hunter <[email protected]> wrote: > > > > Well I would imagine the server component that clients listen to only > > > expect one client to be listening to a given id. > > > > So getting multiple connections to the same channel wont work, maybe > > > they will all actully appear to work, but only (say) the last will be > > > functional. Or when the channel api server forwards a message to the > > > (say) first client, it considers it job done, and ignores the other > > > clients also listening. > > > > ie the server would need to be designed to able to specifically track > > > multiple actual clients listening. Its probably only designed to work > > > with one, even though it may work in some situations > > > > (The point about incepting, say the person using the incepted token to > > > listen, it may well end up disconnecting the original client > > > (physically or virtually). ie still only one works, the original could > > > end up dead) > > > > On 3 May 2011 05:29, Albert <[email protected]> wrote: > > > > > In the documentation, it says... > > > > > "Treat the token returned by create_channel() as a secret. If a > > > > malicious application gains access to the token, it could listen to > > > > messages sent along the channel you are using."[1] > > > > > and then the following section proceeds to say... > > > > > "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.)"[2] > > > > > If someone else gets the token so it can also "listen" to the messages > > > > being sent along the channel, what is stopping me from *legitimately* > > > > giving the same token to multiple users so they can all "listen" to > > > > the same channel? > > > > > Thanks! > > > > > 1http://code.google.com/appengine/docs/python/channel/overview.html#To... > > > > 2http://code.google.com/appengine/docs/python/channel/overview.html#Ca... > > > > > -- > > > > 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 > > > > athttp://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.
