Right, and users that use STOMP are not concerned with how well the solution works for JMS or AMQP users. Although some users may want support for multiple protocols. That's at least four use-cases right there.
An idea that keeps coming to mind -- the computer world has already implemented the tool that "solves all problems" -- it's called a CPU. Our job as developers is not to write the one solution that does everything, but to find a balance and implement the "right size". Which raises the question, "what is the right size?" One messaging solution that meets all needs sounds like a huge challenge. That's like asking for one database solution that meets all needs. I wouldn't want to use a DBMS that handles large warehousing solutions effectively in a small, embedded device. -- View this message in context: http://activemq.2283324.n4.nabble.com/PROPOSAL-Pluggable-Brokers-tp4694058p4694074.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
