jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Neale" <michael.ne...@gmail.com>
Subject Re: Session and server state
Date Mon, 12 Feb 2007 07:30:03 GMT
I think session creation is not expensive, so #2 is perhaps simplest. I
guess the session can act as a cache, but perhaps a cache targeted more
specifically at an application would better serve performance then the
Session itself.


On 2/8/07, Pruitt, Steve <SPruitt@exstream.com> wrote:
> I am interested in managing server state in regards to repository
> sessions.  Specifically, the scenario of a load balancer distributing
> user requests across multiple servers.  There are a number of questions
> that come to mind and I was wondering how others have approached the
> problem.
> In no particular order...
> 1) To avoid recreating a new session per user request, the repository
> session can be cached until the user "logs off".
> 2) Or, if session creation is not expensive then maybe the session is
> committed and then destroyed per user request?
> 3) If the session is persisted across user requests, how can the session
> be serialized to sync up the other servers.
> 4) Or, the session cannot be serialized and server affinity must be
> enforced.
> There may be other and obvious issues, but these are forefront for me.
> Any comments and ideas are appreciated.
> -S

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message