BeaconPush are stopping offering a hosted service as of September 2012. See http://blog.beaconpush.com/post/17708826108/discontinuation-of-cloud-plan
Your options now are Pusher <http://pusher.com> (who I work for) and others listed on my realtime web technology guide<http://www.leggetter.co.uk/real-time-web-technologies-guide> . Regards, Phil @leggetter On Tuesday, 3 April 2012 11:03:52 UTC+1, Aleksei Rovenski wrote: > > You are probably right. We should consider something like beaconpush, > maybe it makes more sense. > > cheers, > Aleksei > > On Monday, April 2, 2012 9:33:54 PM UTC+3, Tom Davis wrote: >> >> On Mon, 02 Apr 2012 07:08:29 -0700, Aleksei Rovenski wrote: >> > Hi all, >> > >> > This is critical and started to happen 2-3 hours ago. >> > First of all connected presence is not coming anymore (disconnected >> comes). >> > This broke a flow in our application (yagoloo-chat). >> > We added a tmp workaround to exclude connected presence handler from >> app >> > flow, but only to find out that messages are now not reaching clients. >> > So client creates the channel and notifies the server that it is ready >> to >> > receive messages, server sends message, but client never gets it. >> > Maybe one out of 20 is getting the message. This is really critical as >> our >> > application is a chat app. >> > Please help, >> >> Not terribly helpful perhaps, but in using the channel API I always had >> to build >> in polling backups because it wasn't uncommon at all for messages to not >> be >> received. Presumably the chat messages are stored somewhere, so how about >> adding >> a timeout such that if the client doesn't receive a message within N >> seconds, >> poll for any missed messages? >> >> Maybe it's just me, but I never considered the channel API to be very >> robust. >> Tokens randomly didn't work, exceptions were raised from the library for >> seemingly no reason, etc. I just use it as a tool to drastically cut down >> on >> Datastore queries, not as the foundation of an application. >> >> > >> > cheers, >> > Aleksei >> > >> > -- >> > 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/-/4PMdsL9OPJIJ. >> > 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. >> > >> >> -- 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/-/WUby-8JKYUgJ. 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.
