jauzennn wrote:
>
> Hello everyone,
>
> First I'd like to say BRAVO!
>
> The whole project is looking awesome! I just spent a couple of hours
> running through all of the pdf files ect and have two questions:
>
> 1) Is there a facility embedded in JServ to manage DB connection pools? I
> couldn't seem to find anything on it.
If you're looking for the J2EE stuff (JDBC connection pooling,
distributed transactions, etc) then only in Tomcat.
If you're not looking for J2EE, or using Java 1.1, then Turbine will do
that for you.
arkin
>
> 2) Are there plans to insert functionality to manage the persistence of
> sessions across JServ instances?
>
> Desc: From what I read, it explicitly stated that if a JServ instance goes
> down in a cluster environment, Apache Will route the
> request(cookie-identified session) terminated with the identifier for that
> JServ instance to another JServ instance, but that the Session data
> associated with that original session is then lost. This, I think, is a
> weakness in the system. Before I get too far into it, I wanted to know if
> anyone was working on anything like that. If not, I have a couple of ideas
> I would like to open to discussion ...
>
> Thanks!
>
> Rich
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
