Jeff McWhirter wrote:
> 
> Brent Welch wrote:
> 
> > I don't think the "fix" is right.  Also, I don't think things are happening
> > the way you describe.  I could be wrong.  In the fcopy docs, when they
> > say the "socket is closed", they mean that, for example, "TclHttpd closes
> > the socket", which is not happening here.  Instead, the remote peer is
> > closing its socket.  In that case, the worst that can happen is that
> > the write by fcopy will get an I/O error.  In that case, the -command
> > callback is still invoked.
> 
> Perhaps it is the platform I am running - win98. The   HttpdCopyDone callback does
> not get called when the client closes the socket. I will try this on a Linux box
> today
> to see if it is win98..

this will happen if the server never tries to read/write the socket
after the client closes it
are you sure an fcopy is is in progress ?


> 
> -Jeff

-- 
Mike Hoegeman
Habanero Technologies, LLC
Phone: 805-279-7306
E-mail: [EMAIL PROTECTED]

Reply via email to