[jboss-dev] JBoss Messaging - to scope or not to scope

[Adrian]

On Wed, 2007-04-11 at 13:44 +0100, Tim Fox wrote:
> Another possibility - and I am sure you will scream in sheer horror when 
> I mention it, would be for JBM to branch our own version of remoting, 
> and rename the remoting packages - then there will be no conflict.
> 
> Any bugs we find in the branched remoting we make sure we re-apply to 
> the main branch.
> 

If you do that then you have to stick with it forever.
e.g. If you want 4.2.x messaging clients to talk to 5.0.x messaging
servers they have to use your cloned api.

Besides all the obvious duplication of code/effort/testing/open ports
it sounds really horrible. ;-)

One of the reasons for using Remoting is that a client can in principle
use the same TCP/IP connection (or whatever transport) for all
communication; jndi, ejb, jms, etc.

Your solution makes this impossible.

But then so does the scoping solution, which is essentially
the same thing. :-)
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx