jackrabbit-dev mailing list archives

hi,
i want to gather some input about how to use jcr sessions in a
web-like environment. so, if a script/servlet that responds to a
request needs to read/write to a repository. of course this largely
depends on the use case. but here are some rules i want to verify:
- in a pure read-only env (i.e. the requests do not write back content
to the repository),
never put the jcr sessions directly into the http sessions.
reason: if you have a lot of http sessions, you end up having a lot
of jcr sessions which might
consume a lot of memory.
- in a pure read-only env, start with 1 session for each request or
share the same session among all requests. if you think this could be
a performance problem, implement a static or dynamic session pool.
- in a mostly read-only env with request-local write back, either use
1 session per request, or a dynamic session pool. important is, that
sessions must not be shared among requests at the same time
(concurrency issues).
- in a r/w env where you need to keep transient changes present over
several requests, you can assign a jcr session to a http session, but
be careful that you don't have them open too long, if you expect a lot
of http sessions.
WDYT?
--
toby