On Fri, 2003-01-24 at 23:58, Andrew Piskorski wrote:
> As far as I've ever known, nothing special happens, the query runs to
> completion as normal. That's certainly what I've always seen happen
> with Oracle. I am not familiar with the nsdb internal, but AFAIK the
> ns_db driver and thus Postgres (or Oracle) doesn't even have any way
> of KNOWING whether or not the web browser is still connected to the
> web server or not.
>
> But... I suspect Steve M. is wondering about the second of these
> threads:
>
> http://openacs.org/forums/message-view?message_id=74443
> http://openacs.org/forums/message-view?message_id=74451
>
Andrew,
Indeed I am and it got me thinking that this 'problem' would apply to
any AOLServer not just OpenACS. I'm curious as to how AOLServer handles
a request.
Would I be right in thinking that it only notices that a request is
closed when it attempts to write a result back?
If this is the case then it probably wouldn't notice until the query
finished and it attempted to return the result. This would imply that
closing the request would have no effect on the query which would run to
completion.
If AOLServer monitors the request and notices that it has gone does it
do anything about it in terms of the processes that are running on
behalf of the request?
If not then I don't see how the situation (in the second thread above)
could occur - Postgres would not be able to distinguish a dead request
from a live one as its running the query on behalf of AOLServer not the
browser.
Steve
--
Steve Manning - Linux Mandrake 9.0 - Gnome 2.0
East Goscote - Leicester - UK +44 (0)116 260 5457
Reply to [EMAIL PROTECTED] - AIM: verbomania
Get my public key from: wwwkeys.pgp.net 25665CAF
--------------------------------------------------
There are only 10 types of people in this world
Those who understand binary and those who don't
--------------------------------------------------
