A strange confluence of ideas...
So someone at work is using 'Jabber', and someone else is implementing a project using messaging. Which made me think - a Jabber JMS provider: sick, twisted, or a flash of inspiration? I'm sure Mr Strachan could knock one up in a jiffy :)
:-). It could also be handy to have a JMS implementation for email, NTTP, Java Groups etc. The downside of this is that the JMS API is quite big and it takes a bit of effort to implement properly.
Maybe the Messenger project's API could provide a simpler entry level API to messaging platforms. Its a facade over the JMS API to
- implement session pooling and abstract away some of the complex threading issues you need to really grok to be able to properly use the JMS API
- seperate the quality of service configuration from application code, so that QoS is specified in an XML deployment document
- makes the JMS API much easier to use
The Messenger API is simple, yet provides access to the core JMS interfaces like the Message interfaces and MessageListener.
So maybe we could extend the Messenger project to make it easy to implement the core Messenger API (and so a subset of the full JMS API) using various existing other messaging transports like Jabber, JavaGroups etc. Very neat idea...