Win32 module problem

[Jon Teichrow <jo...@msoft.com>]

Greetings,

Having a bit of trouble with a module I'm writing.
My current development environment is Win32 hosted
(1.3b7).

During the handling of a request that is aborted
from the client (e.g. user hits *Stop* in browser) my
module is never given an indication that the connection
was terminated.  Not knowing of the termination, 
my module continues to output HTML and eventually
croaks because "r->connection->client" is bogus.  I have
registered cleanup functions but these are not called.  Am 
I not providing a hook I should be?

Thanks.

Re: Win32 module problem

[Dean Gaudet <dg...@arctic.org>]

Use the ap_r*() functiosn such as ap_rputs().  If you don't, then you have
to properly test r->connection->client->aborted ... or something like
that.  Go look at ap_rputs() et al for an example.

Dean

On Thu, 11 Jun 1998, Jon Teichrow wrote:

> Greetings,
> 
> Having a bit of trouble with a module I'm writing.
> My current development environment is Win32 hosted
> (1.3b7).
> 
> During the handling of a request that is aborted
> from the client (e.g. user hits *Stop* in browser) my
> module is never given an indication that the connection
> was terminated.  Not knowing of the termination, 
> my module continues to output HTML and eventually
> croaks because "r->connection->client" is bogus.  I have
> registered cleanup functions but these are not called.  Am 
> I not providing a hook I should be?
> 
> Thanks.
> 
>