No problem, Robert, I'm glad to be of assistance. I wish you luck in developing your app.
My advice would be to have the code responsible for maintaining the connection and passing messages (whether via the Channels API client or EventSource) expose an API to the rest of your app's components, making it straightforward to switch among solutions if you find your use-case shifting, or there's an attractive feature of one solution that you'd like to make use of. Regards, Nick On Wednesday, June 3, 2015 at 4:16:41 PM UTC-4, Robert Stepanek wrote: > > Hi Nick, > > thanks for the extensive feedback! I'm not much into Javascript and > wasn't aware that the EventSource object reconnects on closed > connections - that should suffice for prototyping. I'll look into > opening a feature request if I settle on using App Engine for my > project. > > On Wed, Jun 3, 2015 at 9:26 PM, Nick (Cloud Platform Support) > <[email protected]> wrote: > > I can't comment on the > > GAE roadmap or any timeline for feature implementation but I still > figured I > > would gather a lot of information so you know exactly the state of > > everything. > > That already helped a lot. Thanks again. > Robert > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0c7b4417-fef9-4905-8f80-0bbf8b3768dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
