Hi Garrett, On Sun, Oct 31, 2010 at 10:39 PM, Garrett <[email protected]> wrote:
> Hello Wave Protocol, > Thanks for making such an awesome tool available for public use! > > I'm designing a Public Health Social Action Network and am looking to > utilize the collaborate power of Google Wave. Here is my question: > > If I'm running my own Wave server, XMPP server, SQL user database > server, is it possible to have the client-side front end (the splash, > basically) running internally on my site? I'm wanting to have my users > register their accounts on my site (e.g. [email protected]) and be > able to log into Wave and see our own UI (the same splash UI as Google > Wave's, except running internally on our website). Is this possible > without a great deal of code modification? I hope I made my question > clear... > Sorry for the newbish question. XMPP is only necessary for federation, aka talking to other servers. And currently the expected persistence storage is MongoDb although a SQL layer can be put in as well. So if you'd switch SQL for MongoDb in your setup it should be totally possible to have it running on your internal network. Of course taking into account that you properly block access from the outside world :). I would suggest not using Splash but just our webclient for the front-end, since Splash doesn't seem to support editing. Greetings, Lennard -- 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.
