[google-appengine] Re: Channel API alternatives

Strom, We're recommending Firebase as an alternative to the Channel API. Please have a look at this article on how to use it with App Engine: https://cloud.google.com/solutions/using-firebase-real-time-events-app-engine. As it connects to all manner of clients (web, Android, iOS), we believe

[google-appengine] Re: Channel API alternatives

How nice, another piece of GAE being shut down. As for alternatives, I've found the following four that I'll be looking into: * https://pusher.com/ * https://www.pubnub.com/ * https://www.ably.io/ * https://framework.realtime.co/ On Sunday, October 30, 2016 at 3:58:41 AM UTC+2, PK wrote: > >

Re: [google-appengine] Re: Channel API alternatives

Hello Alexey, You are correct that Pub/Sub is not a complete replacement to the Channel API, and was recommended as a simple lightweight callback communication alternative. The intended replacement is indeed Firebase. As you mentioned, Pub/Sub is designed for pre-defined Topic/Subscriptions,

Re: [google-appengine] Re: Channel API alternatives

Hi Alexey, this has been my understanding too but have never had direct experience with it. I was surprised that Google Support suggested it as an alternative. I still do not think it is. PK > On Nov 3, 2016, at 4:49 PM, 'Alexey' via Google App Engine >

Re: [google-appengine] Re: Channel API alternatives

Cloud Pub/Sub works only between servers -- it doesn't seem like there's server-to-browser push functionality with this, correct? Also, this is explicitly meant for static topic, whereas the old Challen/XMPP stack supported ad-hoc and stateless topic/channel selection and a push from server

Re: [google-appengine] Re: Channel API alternatives

Google Cloud Pub/Sub makes use of Topics and Subscribers. Publishers post messages to a Topic, and the message is either Pushed or Pulled to/by the Subscribers

Re: [google-appengine] Re: Channel API alternatives

Thanks Jordan. How were you thinking that pubsub will work all the way out to the browsers? Thanks, PK p...@gae123.com PS I could write a lot about the first two sentences of your response but I will skip it. I will just say that it is ironic that a low usage platform like GCP makes such bold

[google-appengine] Re: Channel API alternatives

Our goal is to continue to do a better job of delivering reliable, performant, and full featured services. This means deprecating those APIs that have little to zero usage on our system to free up resources for newer, better performing products. The Channel API

[google-appengine] Re: Channel API alternatives

I was just discussing this very point with someone today. Firebase and Channel are not equivalent, which is why Google appears to be pushing this API change. Otherwise what is the point of having API, if implementation details cannot be addressed seamlessly? On Monday, October 31, 2016 at