> > Because it doesn't make sense... See my web-server example.
> >
>
> I guess I don't understand your web-server example. What I thought I
> understood is that you want the server to kill all requests when it gets
> too busy, which may work in your case but makes a serious month-end
> roll-up of accounts impossible. Surely in a web-server application, the
> app itself could keep track of the elapsed time and use a kill request
> call to slaughter its children?

We both agree that a "end of month" query should be able to run
just fine, despite a busy server or whatever else...

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.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com