Tad Glines wrote: > I've been looking at the XMPP protocol specs and and the wave server > code and it looks like I might be able to connect a client to the > server via XMPP. > This would have the advantage of using the existing authentication > infrastructure in the XMPP server. > > I've verified that the client can discover the wave server. > > I'm assuming at this point that the wave server can trust the JIDs > (e.g. [email protected]) coming from the XMPP server as long as the JID > is for a local user. > > I'm not certain what would be best for client-server communication. It > looks like I could probably use the same stuff that's used between > servers, but with a few additions so the client can > subscribe/unsubscribe to waves/wavelets (the equivalent of the open > request in the current client/server protocol). It looks like the > server's aren't actually subscribing to a node, but are just doing > directly addressed publish messages. So the same could be done between > client and server. Basically what you're describing is rolling the client and server into one package. I could see this working for a server/web client setup, however given the nature of federation I'm not sure if a true "client as server and vice versa" setup could actually work.
-- James Purser Collaborynth http://collaborynth.com.au Mob: +61 406 576 553 Skype: purserj1977 twitter: www.twitter.com/purserj GTalk: [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
