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

[Joachim Arrasz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

| 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.

Well, exactly this is what i meant, but ensure that the Class Opencms is
in something like the HASingletonService of JBoss (sry i have no
experience with Weblogic) This should be enough.

| 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

exactly, the modulemechanism is also such a candidate.

| 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.

Yes in my opinion it´s the better solution to have different flexcaches ...

|
| 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.

this is not so easy i tried doing this, but here is no chance to
integrate this without dependencies to a special appserver ...

Achim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDHc5q5IGnahDQXAcRAgnkAJ9sasOh22fjM7R8UBLg68CpzEvTpgCgnRKy
IscqRwRgO+l05VTdS5lXKg8=
=j3C7
-----END PGP SIGNATURE-----