[opencms-dev] more barriers to running in a cluster

[Jason Trump]

Indeed, but thanks for the suggestion anyway.  

I also didn't want to make the whole application a singleton (with an MBean or SessionBean façade for access across the cluster).  It seems like it would be more efficient to let every node have its own copy of the application, and then provide different implementations of those services that require distributed logic.

I think this is the list of services that need distributed logic if the system is to run correctly on a cluster:

UUID generation
Event dispatching
Search indexing
Resource locking

The flex cache would also be a candidate, but I think it's ok to let each node in the cluster manage its own cache, and then just use the distributed event service to clear the cache when necessary.

I think some support for connecting to the database through a named DataSource (rather than a JDBC URL) would be a good idea, as well.

-jason

> -----Original Message-----
> From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-
> bounces at opencms.org] On Behalf Of Joachim Arrasz
> Sent: Tuesday, September 06, 2005 11:08 AM
> To: The OpenCms mailing list
> Subject: Re: [opencms-dev] more barriers to running in a cluster
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> sorry for the mistake in the previous mail.
> I forgot that you use WebLogic ;) So the HASingletonService must be
> replaced with something similar from Weblogic
> 
> Sorry
> 
> Regards
> 
> Achim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFDHbDb5IGnahDQXAcRAhL+AKDR57vVKp7w1J6xn3WOUWpv4uSobgCg3UsQ
> IKT8dcGzVi1A5yltOiXA6Go=
> =4jNk
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev