I'm using DBISAM for the back-end of a website. My question is, should
I create a single session with a separate database for each connection,
or should I give each connection its own session (probably from a pool)?

Any advice appreciated -

Regards, Glynn

Glynn,

Not knowing exactly *how* you are using DBISAM as a back-end can make a
big difference, but in general, for multi-threading you should create a
separate Session, Database, Table(s), and Query(ies).

Regards,

Jason Lee

Glynn Owen [RTC] wrote:
> I'm using DBISAM for the back-end of a website. My question is, should
> I create a single session with a separate database for each connection,
> or should I give each connection its own session (probably from a pool)?
>
> Any advice appreciated -
>
> Regards, Glynn

Glynn,

<< I'm using DBISAM for the back-end of a website. My question is, should I
create a single session with a separate database for each connection, or
should I give each connection its own session (probably from a pool)? >>

If you're using ISAPI, then you'll need to make sure that each connection is
given its own session, database(s), table(s), etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Glynn,
>
> << I'm using DBISAM for the back-end of a website. My question is,
> should I create a single session with a separate database for each
> connection, or should I give each connection its own session
> (probably from a pool)? >>
>
> If you're using ISAPI, then you'll need to make sure that each
> connection is given its own session, database(s), table(s), etc.

Thanks. That's what I did, but there was some question about that from
other folks, so I thought I would ask.

Regards,
Glynn

--
http://realthinclient.com