JBoss development,
A new message was posted in the thread "Partition and Node identities":
http://community.jboss.org/message/529470#529470
Author : Brian Stansberry
Profile :
http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
IMHO what you've laid out makes sense and is the way to move forward. I posted a link
back to this thread on the other one, in case anyone following that forum wants to weigh
in.
Re: JBossTS, I really just linked that because you're a smart guy and I wanted you to
be aware of the entire problem domain; i.e. we've got use cases that need ints and
others that need strings.
For the JBossTS case there's no need to come up with a port, just an int. The only
reason that particular socket exists is to generate a unique-on-the-host int. They create
the socket bound to 127.0.0.1 and then they can use the port number as a unique id because
they know no other process could concurrently do the same thing. The whole thing is
pluggable, and if another technique were available the whole socket would go away.
But hashing the name would still leave the chance of collisions.
Re: HornetQ, yeah, I hope the need for an int goes away, and my guess is it does. We can
find out quickly enough; either when those guys get back from meetings or in a day or so
when I get a minute to poke around in their AS integration branch to see.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/529470#529470