Thank you for the _very_ useful and informative reply. :) > AppEngine actully has XMPP > intergtationhttp://code.google.com/appengine/docs/python/xmpp/
Yes, but from I can gather, I would need to run an XMPP server somewhere to handle the chats (or find a free provider X), and because chat is not the main function of my app (I'm building a go board game server) and needs to be integrated with the rest of the application, it's not the ideal choice. > And the Channel API http://code.google.com/appengine/docs/python/channel/ This was actually extremely interesting and I think I'll consider this to get rid of the polling. However, because each user can only have one channel open, I need to do similar logic to polling on server-side anyway (i.e. merge messages from different channels), so my data structure problem still remains. > Could probably use the matcher API (renamed Speculative Search > API)http://groups.google.com/group/google-appengine/browse_thread/thread/... > to perform dispatching of messages, again eliminating the need for the > polling on the datastore. It seems this is still in very early testing phase. Because I don't yet have the user numbers that would require this infrastructure, I think I'll be doing without for the time being, and rewrite the merging functionality using matcher API when it's open to all App Engine users. (Don't think I should apply for testing when I only have a few concurrent users at most :) -- 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.
