Thanks for your feedback. I should have guessed. I'm not sure if there's much point for me in developing the REST architecture on GAE and then using something else for XMPP -- especially if I have to manage users across the systems.
The XMPP implementation is... not well thought out :( bjorn On Jan 16, 5:21 pm, Ryan <ryanleeschnei...@gmail.com> wrote: > Last I looked GAE's XMPP is limited to just sending <message/> stanzas > to your application, and having the application respond with a reply > <message/>. If you want to do anything more complicated with XMPP you > have to use your own servers or server components on some other > infrastructure. That said, you could still develop the REST interface > on GAE, and have your own XMPP server component act as a "proxy" to > the REST interface by marshaling incoming <iq/> request/responses to > the REST interface. Running your own XMPP servers on cheap linux > hosts and/or scaling server capacity with Rackspace or Amazon seems > like a viable solution (with all your data load on GAE you can just > use as many of the cheapest Amazon/Rackspace instances you need to > maintain client connections). > > I'd love to see "full" support for XMPP on GAE, but given XMPP's > stateful nature I doubt we'll see it any time soon, if at all. > > Thanks, > Ryan > > On Jan 16, 9:04 am, Bjorn Roche <bj...@xowave.com> wrote: > > > > > Hey all, > > > I am planning to build a web app that provides ReST and XMPP to > > custom-built clients. GAE seems like a good choice as google talk is > > supposed to be part of the package, but I'm confused about how > > authentication works with web vs XMPP. I realize I can either do my > > own authentication or use google accounts for the web services. > > > With Google accounts authentication, how would the clients > > authenticate into XMPP? Would it be sufficient to ask the user for > > username/password? I assume that would get the user into XMPP, but not > > the web services, since google protects its account login services > > when doing this on the web. If this does work, what are the > > implications? I'm not going to be able to build in features like > > facebook connect, etc, right? What about portability away from Google? > > > If I manage my own user accounts, how can the clients use google's > > XMPP services? Is this possible? I don't see any way to create XMPP > > accounts or anything like that (user-n...@my-app.appspotchat.com seems > > like something I should/could manage, but I don't see an API. If I let > > everyone log in with the same account, can I prevent them from > > changing the password?). > > > Any advice here is appreciated. Thanks, > > > bjorn > > > ----------------------------- > > Bjorn Rochehttp://www.xonami.com > > Audio Collaboration -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.