[opencms-dev] Database connection pooling
Evans, Michael
EvansM at visa.com
Fri Feb 21 11:42:31 CET 2003
1. I completely agree that using container managed database pooling would
be very nice. The only problem I have with OpenCMS's internal db pooling is
that it doesn't detect when the server drops a connection / doesn't
reconnect it. Perhaps this will happen as part of the EJB migration project
(which is currently on hold)-8.
4. I don't know the exact ins and outs of the cache mechanism, for dynamic
pages that change regularly (or use random elements) its often best to turn
cacheing off for that page - see the FAQ docs for examples.
You can include static content in the OpenCMS virtual file system, or if you
make sure they aren't in the opencms directory then you can have the web
server dish them out as normal.
Mike
-----Original Message-----
From: Vadim Lotarev [mailto:vlotarev at evelopers.com]
Sent: 21 February 2003 09:36
To: opencms-dev at www.opencms.org
Subject: RE: [opencms-dev] Database connection pooling
Evans,
Thank you for the answers. Could you please answer some more?
>1. Not all app servers provide connection pooling. Also the where class
>names vary between implementations OpenCMS would then start to become
>product specific.
JDBC 2.0 specification has standart approach to access datasources (using
Datasource-related interfaces). I think that usage of these interfaces is
not product-specific approach. In addition to this I can proclaim that ANY
of modern application servers support connection pooling, especially those
ones which support JDK 1.4 specification required to use the last version of
your product. Do you belive that your realization of connection pooling is
better than app servers manufacturer's?
It seems that this is the good time to revise this approach ...
>4. Scaleability of end users visiting sites is excellent (with options to
>static export content for greater scaleability), scaleability of
interactive
>users modifying content is moderate.
Apart from using static export can you explain in what way OpenCMS
determines that content has been changed and it is necessary to update
cache?
One more question: is it possible to use OpenCMS to manage dynamic content
only and not to operate on static part of site (may be coded manually)?
Thanks in advance,
Vadim Lotarev
More information about the opencms-dev
mailing list