Yes, echoey hasn't been updated in a while so isn't compatible with the document model. I have an almost-finished patch that fixes echoey that I'll put out for review when I have the chance to finish it.
On Wed, Nov 11, 2009 at 10:50 AM, James Purser <[email protected]>wrote: > > On Wed, 2009-11-11 at 09:53 +1100, Joe Gregorio wrote: > > On Tue, Nov 10, 2009 at 11:23 PM, maxsap <[email protected]> > wrote: > > > > > > Hello all, I am developing robot and currently I am using an xmpp > > > server my question is if the wave protocol is 100% compatible with a > > > regular xmpp server (e.g. openfire,or a xmpp RA)? > > > > The FedOne server runs as a XEP-0114 compliant extension and can run > against > > any compliant XMPP server. In the FedOne codebase is echoey, and example > > agent, which is a good place to start if you are building a robot: > > Speaking of Agents under FedOne, I've noticed that either the Client > seems to be slightly broked or the Agents output hasn't been brought up > to speed with the new conversation model. > > I'm running an echoey on my own server (latest HEAD) and it connects to > the server fine and can be added to a new wave fine, however any output > from the wave is not getting displayed in the client. The logs indicate > that everything seems to be working fine in the background. > -- > James Purser > Collaborynth > http://collaborynth.com.au > http://wavingtheshiny.collaborynth.com.au > Mob: +61 406 576 553 > Skype: purserj1977 > Twitter: http://twitter.com/purserj > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
