> -----Original Message-----
> My example was this:
> Imagine a ISAPI application that processes queries to a
> Firebird database.
> These queries will run endlessly (no timeout). Some of the
> queries are somewhat "heavy".
>
> Connections are pooled in the ISAPI dll.
>
> A user asks for a webpage with a heavy query. But the server
> is busy and is slowish.
>
> Here's what happens:
> - user asks for page
> - ISAPI dll will take a connection from the pool and process query
> - query runs...
>
> - user gets annoyed and uses "Refresh" button
> - ISAPI dll will take a connection from the pool and process query
> - query runs...
>
> If there was a timeout, the ISAPI dll could respond with a
> "busy" page instead and let the user know what's going on.
> Obviously, a "cancel"
> button doesn't work here.

Good point, this scenario would probably do the same with .net's db pool,
not sure about php!

Rgds

Si Carter
http://www.tectsoft.net/
http://www.fbtalk.net/