> > 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.
>
> Indeed, but a timer and a "kill query" will work.
> (Just to be clear: the timer is on the client side, which in your
> example is the web server)

Ah yes - but the point it, it COULD be in the database engine, given
that that's the final point of execution.

With regards,

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