Re: [Modeling-users] Database Connections

[Sebastien B. <sbi...@us...>]

And BTW, I suspect that if you've already given a try to the
ECSessioning module, or thought aboyut using it, then all the sessions
probably lie in the same process --or it would have been useless.

  So, now, I see the moment coming where you'll ask whether it's
  possible to have a dedicated db-connection per EC; is that it?

You also wrote:
> What they meant by pooling is not what Oracle developers usually mean;=20
> they want to be sure that for every HTTP Session, and all of it's HTTP=20
> requests, there is a single connection to the database that is reused=20
> for the entire length of the session lifetime.

  In other words, does it mean that "for each session's EC there exists
  one and only one connection to the db"??

If this is the case, then we'll need an other ObjectStoreCoordinator,
assigning a dedicated DBContext to each EC... Hmmm, just thinking loudly
here, okay, I'll wait til you confirm the need for such a feature.

-- S=E9bastien.


Sebastien Bigaret <sbi...@us...> wrote:
>         Hi Duncan,
>=20
>   Before answering and since I've never used the mod_python and any of
> its session management tools, could you please tell:
>=20
> - which session management module you intend to use?
>   (http://www.modpython.org/FAQ/faqw.py?req=3Dall#3.8)
>=20
> - how does it work? I mean, from a process or thread perspective, can
>   you be more explicit?
>=20
> In short, the answer depends on the answer of those questions; the
> EditorContextSessioning component only provides an easy way to register
> and retrieve the EC based on a session id. The number of connection to
> the database is independent to this component, and is usually 1 (one)
> per process (I really mean process here, not threads, a DB connection is
> shared by threads within a single process). That's why I asked about the
> way mod_python + the session management module you'll use handle
> sessions wrt processes.
>=20
> -- S=E9bastien.
>=20
>=20
> Duncan McGreggor <py...@ad...> wrote:
> > Hey Folks,
> >=20
> > We're building an application that uses Modeling, and a couple question=
s came
> > up in a meeting today. The biggest concern was about sessions (what they
> > called database pooling or connection pooling). I did have a look at
> > EditorContextSessioning, and let them know about it, and it looks like =
it will
> > suite our needs. However, I wanted to get some explicit feedback, just =
to be
> > sure ;-)
> >=20
> > Application Activity: there's going to be lots of querying, searching, =
and
> > updating (the last to a lesser degree).
> > Application Framework: Apache + mod_python with the mod_python Session =
object
> > for session management
> >=20
> > What they meant by pooling is not what Oracle developers usually mean; =
they
> > want to be sure that for every HTTP Session, and all of it's HTTP reque=
sts,
> > there is a single connection to the database that is reused for the ent=
ire
> > length of the session lifetime.
> >=20
> > Is that, in a nutshell, what we get when we use EditorContextSessioning?
> >=20
> > Thanks!
> >=20
> > Duncan