[jbosscache-dev] Re: Non Blocking State Transfer Status (& Integration with JGroups)
Jason T. Greene wrote:
<snip/>
Although IMO a bare tcp
connection would still be the most optimal form of transferring large
state to a single node since the kernel and the hardware is doing all
the work. That can be saved for a future optimization though ;)
Semi-OT: The week before the holidays I largely spent helping with some
security certifications for the AS. Had to explain every
clustering-related port the AS used, how it was bound, secured, could be
controlled by an admin etc.
Now I'm updating the AS Clustering Guide, trying to write
user-understandable docs about how clustering works. A big conceptual
barrier is always the multiple JGroups channels. The shared transport
helps some with this (although AS 5 is still not optimal in this regard,
so it uses 2 separate transports).
What I'm driving at is both of these efforts leave me with a queasy
feeling about adding new and different ways of opening sockets and
communicating around a cluster. OK if needed as an advanced optimization
for the real hard core cases, but IMHO there's a lot of value in keeping
it simple by default.
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com