I thought the entire client/server relationship was JSON or XMPP... On Nov 25, 6:43 pm, Trejkaz <[email protected]> wrote: > On Thu, Nov 26, 2009 at 12:32 AM, Venkat Polisetti > > <[email protected]> wrote: > > Currently Google does not support hosting Robots on servers other than > > the App Engine. In the future it will, I hope. > > Set up an XMPP server somewhere for your domain, set up a Wave server > attached to that. Bots can then connect via that Wave server's > client-server protocol. > > pros: > - Uses a protocol designed for this sort of thing -- XMPP -- not > HTTP, which was never meant to be used as a two-way push protocol. > - Works through the already documented federation protocol. > - Puts control of the bot protocol back in the hands of the person > setting up this server. I haven't looked at how FedOne does it yet > though. > - Potentially allows you to write bots which run inside the > component itself, saving the need for any client-server protocol > whatsoever. > > cons: > - Main server doesn't seem to support federation yet -- but it > *will*. (sandbox does though, right?) > - Federation might not support things like filtering which events > to receive since it isn't truly designed for bots. Someone who is > online (and bots always are) will always receive all updates. > - There aren't many Wave servers to choose from (I could only name > FedOne myself before doing a Google search to find a couple of > others.) > > Personally I think that this kind of setup makes a lot of sense for > bots though. If you made the client-server protocol based on XMPP as > well then there would be a large number of different programming > languages it would be possible to program in. > > TX
-- You received this message because you are subscribed to the Google Groups "Google Wave API" 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-wave-api?hl=en.
