Re: [Modeling-users] Database Connections

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

        Hi Duncan,

  Before answering and since I've never used the mod_python and any of
its session management tools, could you please tell:

- which session management module you intend to use?
  (http://www.modpython.org/FAQ/faqw.py?req=3Dall#3.8)

- how does it work? I mean, from a process or thread perspective, can
  you be more explicit?

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.

-- S=E9bastien.


Duncan McGreggor <py...@ad...> wrote:
> Hey Folks,
>=20
> We're building an application that uses Modeling, and a couple questions =
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 ob=
ject
> for session management
>=20
> What they meant by pooling is not what Oracle developers usually mean; th=
ey
> want to be sure that for every HTTP Session, and all of it's HTTP request=
s,
> there is a single connection to the database that is reused for the entire
> length of the session lifetime.
>=20
> Is that, in a nutshell, what we get when we use EditorContextSessioning?
>=20
> Thanks!
>=20
> Duncan