I am looking to use the XMPP service as a form of 'broadcast push' to authenticated users of the app...
ie when content changes on the backend the server would post a message to a group chat front-end clients would be listening (I guess via strophe.js) to particular group chats This seems more efficient than the Channel API where I'd have to maintain a channel per user, even though there are no user-specific messages that need to be sent, only broadcast changes to all users. But... the docs are completely unclear on how I would authenticate users, i.e. prevent unauthorised users to listening to the updates chatroom. >From what little I've read XMPP has TLS and SASL for this purpose but I can't find anything written about those in conjunction with GAE. >From messages on this list it sounds like I'd in fact need a whole other XMPP server to manage user accounts... or... it's completely unclear basically. -- 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.
