Hi everyone 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". For the jabber process receiving the workitem from the JabberParticipant, it will need to be in a format that doesn't make loading ruote a requirement. So I'm considering serializing to JSON in this case by default, and using workitem attributes to possibly specify alternate formats (XML or YAML). The second issue I need to address is using a single Jabber connection, currently the listener and participants open their own connections. This is fine, the XMPP protocol does allow for the same JID to be used multiple times. Currently I specify different resources for the Listener/Participant, making it easy to send a message directly to the listener process. The roster management is currently dynamic as well. It will clear the roster when it starts, except for a hard coded list of contacts. As messages are sent out the roster will be populated with those JID's, making sure that the listener will respond to replies. There is some toughening up to do here, which I will do now, to ensure messages are only parse when they come from contacts on the roster. Here is my todo list for the next hour or two: * Documentation * JSON serialization of workitems by default, option to do XML/YAML * Improve message handling by checking sender against the roster * Ability to share a single connection between the Participant/Listener Ciao -- Kenneth Kalmer [EMAIL PROTECTED] http://opensourcery.co.za --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
