I think the only client implementation for the channel API is the JavaScript one. I'd love to be wrong though.
If there is a way to set up a Java (or Python or Go) client for the channel APIs, you would end up with semi-persistent http connections between channel service and backend. I don't know what that would do to the rest of the backend's processing, but it could hardly be worse than paying for nine extra backend instances... - Kris On Wednesday, August 8, 2012 10:47:09 AM UTC-7, Brandon Wirtz wrote: > > I don’t have time to build a solution write now, because we are too close > to our own product launch, but in thinking about this I wondered about > Channel API between servers…. > > > > This is a solution I have been thinking about and if someone knows why it > won’t work that might save me some headache or might reduce theirs if it > works. > > > > Could you not have frontends use the channel API to send the data to the > backend. The data would be streamed to the backend and the buffer in the > channel would allow the backend to read the stream of data in to its > memory. The calculations could be done, and then written to datastore and > memcache so that when the client re-polled the scores would be correct and > shared? > > > > > -- 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/-/YeQXS6tNPfQJ. 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.
