On Wed, Nov 26, 2008 at 7:53 PM, Kenneth Kalmer <[EMAIL PROTECTED]> wrote: > > I've just pushed a working JabberParticipant and JabberListener to my > ruote fork at http://github.com/kennethkalmer/ruote for review. > > So far it works beautifully in my test cases, with one or two problems > I can anticipate in the wild. Particularly working with serialized > InFlowWorkItem instances. Using ruote-rest with HTTParty, I've gotten > used to manipulating the InFlowWorkItem in JSON format. It works very > well, and the wrapper class handles "manages the integrity of the JSON > InFlowWorkItem".
Hi Kenneth, I pulled it in my ruote/master : http://github.com/jmettraux/ruote/commits/master/ Thanks a lot ! I will try to write some summary documentation for it at http://openwferu.rubyforge.org/participants.html mostly linking to your inline documentation. Looking forward to the evolution of this participant/listener pair. A quick newbie question, why the Jabber label and not the XMPP one ? Is it not pure XMPP ? Ciao ! -- John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruote (OpenWFEru) users" 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/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
