Re: Database Connections

On Aug 6, 2004, at 3:33 PM, Sebastien Bigaret wrote:

> Now, this can be fine... or not, depending on the type of application
> you're currently building (I mean, its characteristics, esp. if you can
> expect heavy load).

We're expecting very light load.

> For example, say that some of fetches can take some time --can you wait
> for a fetch to be finished before serving others?

We are expecting that there will be some delays perceived by users 
during regular use as you describe here. This is okay :-)

> If your app. does not
> fetch a lot, maybe it's not a pb, but if most of its requests end up
> with one or more ec.fetch() then the default behaviour will probably 
> not
> be suitable.
>
> And again, could you be more explicit whether in your first mail you
> meant that "for each session's EC there exists one and only one
> connection to the db"??

Sorry about responding so late; did my last email make this more clear, 
or should I send along more details/better explanation?



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com