--
David W. Taylor
Developer | SL Corporation | http://www.sl.com
david.taylor_at_sl.com | Tel: +1.415.927.8555 | Fax: +1.415.927.8401
________________________________
 
Email communication may contain privileged or confidential information
proprietary to SL Corporation. If you have received this communication in
error, we ask that you advise the sender by reply e-mail and immediately
delete the message and any attachments without copying or disclosing the
contents.
 
From: Shreedhar.Ganapathy_at_Sun.COM [mailto:Shreedhar.Ganapathy_at_Sun.COM] 
Sent: Monday, June 23, 2008 12:44 PM
To: users_at_shoal.dev.java.net
Subject: Re: [Shoal-Users] Is there any up-to-date 1.1 documentation?
 
Hi David 
Glad to know that Shoal might meet your clustering needs. 
We will work on a formal document covering changes going into 1.1 as soon as
possible. 
I have updated the Javadoc for reportJoinedAndReadyState() in
GroupManagementService
<https://shoal.dev.java.net/nonav/docs/api/com/sun/enterprise/ee/cms/core/Gr
oupManagementService.html>  to better explain the behavioral semantics. This
will be captured in more detail in our wiki page. (I had written a blog
<http://blogs.sun.com/shreedhar/entry/sailfin_drives_a_new_feature>  entry
earlier with the Sailfin driven use case but that does not explain the
functionality in granular detail.) 
Among the higher level changes to 1.1 are :
1. Ability to specify a specific NIC address to bind to.
2. Fine tuned state machine wrt health monitoring. Additional transitional
states have now been added to reflect the state of a member from starting
through to stopped/dead. 
3. Ability for the application to report its joined and ready state to
service requests. Added api in Join notification signal, getMemberState()
allowing consuming components to query the health state of a member when a
join notification signal is received. 
4. Ability to specify a member as a bootstrap node with a URI (specified on
all members) that will allow members to communicate with that member as a
software router when no multicast is available or when the members are
across subnets. 
5. Ability for each member to participate in multiple groups. 
6. Better resilience in health monitoring with respect to network issues,
and hardware failures.
7. Fixes for a number of bugs reported in Shoal, GlassFish, and Sailfin
projects. 
Let us know if you have any other specific questions.
hth
Shreedhar
David Taylor wrote: 
Hi folks,
 
First time posting.  I'm excited about Shoal.  It seems to be exactly what
we need to add clustering to our application.
 
Does anyone have any documentation on the changes that are being worked
through for 1.1?
 
I am about to start a prototyping effort and it sounds like I should use 1.1
from the CVS repository.  Are there any written guides to object interaction
that I can consult?  I'm basing most of my understanding on the "Clustering
with the Shoal Framework" article at
http://today.java.net/pub/a/today/2007/12/11/clustering-with-shoal-framework
.html and the JavaDocs.
 
Is there a new document that discusses the recent 1.1 additions such as
gms.reportJoinedAndReadyState(groupName)?
 
Thanks.
 
David
--
David W. Taylor
Developer | SL Corporation | http://www.sl.com
david.taylor_at_sl.com | Tel: +1.415.927.8555 | Fax: +1.415.927.8401
________________________________
 
Email communication may contain privileged or confidential information
proprietary to SL Corporation. If you have received this communication in
error, we ask that you advise the sender by reply e-mail and immediately
delete the message and any attachments without copying or disclosing the
contents.