The Java (or Python) client library could connect to the XMPP layer directly and on the other side provide developers with an interface similar to the interface provided to Javascript users on the browser. This would effectively hide the XMPP and related XML messages Robert is talking about. Of course Google would have to provide such a library as it provides the Channel API Javascript in the browser. Maybe this approach is not implementable but I can not see why because I have so little information about the internal workings of the Channel API system. I was hoping someone from Google could enlighten us and settle once and for all if we could use the Channel API on clients other than browsers.
On Nov 4, 5:27 am, Robert Kluin <[email protected]> wrote: > My understanding is that the Channel API uses XMPP on the back end to > 'connect' to Google's internal 'comet servers.' One of the big > advantages this approach is that your app's client does not need to > know about XMPP, or be able to process the related XML messages. > Instead you can use HTPP and JSON; that _potentially_ lets you build > a simpler client. > > Unfortunately, from Peter's comments it sounds like the underlying > mechanism is still complex. > > Robert > > On Wed, Nov 3, 2010 at 13:19, dilbert <[email protected]> wrote: > > Peter already answered some of the questions in my previous post. It > > was posted about half a day ago but since it was my first post in this > > group it got stuck in the approval process. > > > On Nov 3, 8:24 am, dilbert <[email protected]> wrote: > >> I think that the Channel API uses XMPP under the hood (as mentioned > >> here:http://www.youtube.com/watch?v=oMXe-xK0BWAatabout 13:20). > >> I do not see why we could not have a Java or Python client library for > >> Channel API. There is some information about it in this thread (http:// > >> groups.google.com/group/google-appengine-java/browse_thread/thread/ > >> d0401a784d4171c8). Posts 9 and 10 are relevant. It would be nice if we > >> could use the Channel API on Android. Maybe an issue (feature request) > >> should be raised. > > >> @Peter - are You saying that a Java client library to use with the > >> Channel API would be impractical/impossible to implement. Could You > >> elaborate a bit. > > >> On Nov 3, 5:37 am, Robert Kluin <[email protected]> wrote: > > >> > Are the data-exchanges overly complicated? > > >> > I have used XMPP for an app, I was hoping the channel API would let me > >> > simplify. > > >> > Robert > > >> > On Wed, Nov 3, 2010 at 00:29, Peter Petrov <[email protected]> wrote: > >> > > Forget about emulating it outside of a browser. Your best bet is using > >> > > a > >> > > separate mechanism for sending messages to non-browser clients - for > >> > > example > >> > > make a HTTP postback, or send a XMPP message. > > >> > > On Wed, Nov 3, 2010 at 6:20 AM, Robert Kluin <[email protected]> > >> > > wrote: > > >> > >> Have you look at the communications at all? I the javascript file is > >> > >> included in the SDK. It is a little "heavy," but you could probably > >> > >> use firebug (or chrome/safari dev console) to figure out what is going > >> > >> on. > > >> > >>http://code.google.com/p/googleappengine/source/browse/trunk/python/g... > > >> > >> Robert > > >> > >> On Tue, Nov 2, 2010 at 08:41, Tomas Alaeus <[email protected]> wrote: > >> > >> > I for one thought directly of games when I heard that the Channel > >> > >> > API > >> > >> > were coming to AppEngine. However, all discussions and articles only > >> > >> > mentions a Javascript client running in a web browser. Will it come > >> > >> > ports to other languages as well? Maybe the actual communication is > >> > >> > so > >> > >> > simple that it is trivial to do oneself (considering that the API is > >> > >> > somewhat similar to websockets if I understood it correctly)? > > >> > >> > Thanks, Tomas > > >> > >> > -- > >> > >> > 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. > > >> > >> -- > >> > >> 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. > > >> > > -- > >> > > 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. > > > -- > > 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.
