On each server in the cluster, the initialization will be done identically, in parallel, resulting in equivalent registries.
Christian is right; to support multiple apps in a single context, it is necessary to use qualified servlet context attribute names. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com > -----Original Message----- > From: Christian Essl [mailto:[EMAIL PROTECTED] > Sent: Monday, September 15, 2003 9:39 AM > To: Jakarta Commons Developers List > Subject: Re: [HiveMind] I don like HiveMind.getDefault and > setDefault(Registry) > > > > What if you had two applications running under the > > same context though? > I guess they should have (as recommended by the > servlet-spec) have attribute names like > [package-name].HiveMindRegistry. (Of course if you mean two > Tapestry apps you will have to find another way). > > > And how will replication be taken care of, I thought > > context attributes > > are not replicated in a clustered environment. > > As I see the war is distributed and on each node it > will be started up seperately. Therefore the > ServletContextListener. However I am not so common with clusters. > > > > And,yes the > > constructDefaultRegistry will definitely be helpful. > > > > -Harish > > > > > __________________________________________________________________ > > Gesendet von Yahoo! Mail - http://mail.yahoo.de > Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
