W3C home > Mailing lists > Public > www-lib@w3.org > January to March 2003

RE: Bug in HTRequest_setOutputStream???

From: Mark Boudreaux <mboudreaux@citadel.com>
Date: Thu, 20 Feb 2003 13:59:41 -0600
Message-ID: <714EB841B8E8024D91E725F6E3F5F7390A0744@citadelex.corporate>
To: "Richard Atterer" <richard@list03.atterer.net>, <www-lib@w3.org>

> -----Original Message-----
> From: Richard Atterer [mailto:richard@list03.atterer.net]
> Sent: Thursday, February 20, 2003 12:06 PM
> To: www-lib@w3.org
> Subject: Re: Bug in HTRequest_setOutputStream???
> 
> 
> On Thu, Feb 20, 2003 at 07:21:47AM -0600, Mark Boudreaux wrote:
> > I am a little confused by your post.  My proposed change to
> > HTRequest_setOutputStream() does not free the stream object.  Can
you
> > show me where you are referring to?
> 
> The way I understand it, HTReqMan.c is written not to delete the
output
> stream, only to call its free() method when the request object itself
is
> deleted.  For this reason, it also seems to "wrap" the output stream
you
> pass to HTRequest_setOutputStream() inside another HTNoFreeStream
object.
> (I'm not too sure why the extra HTNoFreeStream is actually needed.)
> 
> Your change sets "me->output_stream = output", so later
HTRequest_delete()
> will execute "HTNoFreeStream_delete(me->output_stream)".
> 
> Cheers,
> 
>   Richard

On a second look you are correct.  Thanks for the insight.  I was solely
focused in one module and not looking at everything as a whole.

Mark
Received on Thursday, 20 February 2003 15:09:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:43 GMT