http://www.xmlblaster.org/ looks like it has almost the same project scope. The biggest difference is that their protocol is based on XML. Maybe join two projects?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very interesting! They are using the benefits of CORBA and XML.
The thinking with OpenQueue so far has been to require of the users only the minimum of other tools. So while you can send an XML message in OpenQueue, you are not required to, and thus your implementation doesn't have to include an XML parser (and XPath processor, which xmlBlaster also uses). But one advantage of using XML throughout the system is that the server can do more intelligent filtering of messages, not just of the message content, but of the meta information, too (who sent the message, when, how).
Let's post a message to the xmlBlaster mailing list so we can open a dialogue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another difference is the reliance on an orb. There are people out there who don't need or want to use one. Could possibly accomplish this with a classing scheme like the one in the persistent mechanism message I posted earlier.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
http://www.xmlblaster.org/ looks like it has almost the same project scope. The biggest difference is that their protocol is based on XML. Maybe join two projects?
Very interesting! They are using the benefits of CORBA and XML.
The thinking with OpenQueue so far has been to require of the users only the minimum of other tools. So while you can send an XML message in OpenQueue, you are not required to, and thus your implementation doesn't have to include an XML parser (and XPath processor, which xmlBlaster also uses). But one advantage of using XML throughout the system is that the server can do more intelligent filtering of messages, not just of the message content, but of the meta information, too (who sent the message, when, how).
Let's post a message to the xmlBlaster mailing list so we can open a dialogue.
Another difference is the reliance on an orb. There are people out there who don't need or want to use one. Could possibly accomplish this with a classing scheme like the one in the persistent mechanism message I posted earlier.