Aaron Johnson sent the following bits through the ether: > What type of messaging systems are in use in your organization?
Have you looked at the Java Message Service? http://java.sun.com/products/jms/ O'Reilly has a great book on the subject which covers all the main points (but doesn't go into too much detail). Email is used everywhere I've worked for bugtracking, alerts, etc, although we use SOAP for some messaging at my current company. > What is the most important messaging system in your organization? Well, email, by default. > Is someone else is already thinking of doing or done work in this area > that would like to collaborate? I've been thinking of doing something similar to the JMS but for Perl (not that I have a lot of free time, of course ;-). PMS doesn't have a great ring to it, however. As with all these Java things, it is simply an API. I had imagined a Spread implementation, but I'm not sure that will cope with the Point to Point part of JMS. > These efforts would be different from Spread. I don't see how this is different. Messaging systems simply push data around. Business-orientated messaging systems are reliable, don't lose messages, queue up messages when a client is down etc. Spread can do this. So can email. We'd just have to build the API and worry about an actually implementation seperately. HTH, Leon -- Leon Brocard.............................http://www.astray.com/ Nanoware...............................http://www.nanoware.org/ .... "Beulah, peel me a grape."
