W3C home > Mailing lists > Public > www-lib@w3.org > April to June 2000

Any ideas on this?

From: Desrochers, Gary <Gary.Desrochers@fmr.com>
Date: Mon, 10 Apr 2000 09:05:34 -0400
Message-ID: <6146FA7F7068D21184DD00A0C9B57D4003D9F795@msgmmk530nts.fmr.com>
To: "'www-lib@w3.org'" <www-lib@w3.org>
Good Morning,

	I am a little confused on HTEvent_unregister.  Since the event has
been registered and a timer has been set up which is associated with a
socket.  How libwww does not call HTEvent_unregister whenever it does a
NETCLOSE and the event is deleted?  The problem is that the event is deleted
but is still attached to the SockEvent?  The SockEvent is still attached to
a timer.  When the timer goes off the Handler is called and then the event
is dereferenced as to where to call.  Of course, the event no longer exists.
The only two things which break the connection between the
timer->SockEvent->Event is the HTEvent_unregister or if the same file
descriptor is created and HTEvent_register is called.  If a different file
descriptor is used the next time through the event loop the old timer
associated with the old socket is found and any program will crash.

I saw this in several places.  There was one very descriptive post:
http://lists.w3.org/Archives/Public/www-lib/1999AprJun/0263.html
If you follow the post you will see what I am talking about.

I event noticed that some of the HTEvent_unregister calls were removed?  Why
is this?

If the library is calling NETCLOSE and then making the socket INVSOC then
why is the event/timer not unregistered?

Gary.Desrochers@fmr.com
Received on Monday, 10 April 2000 09:06:09 GMT

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