- From: Mark D. Anderson <mda@discerning.com>
- Date: Fri, 11 Jun 1999 12:35:02 -0700
- To: <jose.kahan@w3.org>
- Cc: <www-lib@w3.org>
>In this >loop we have a select() function, which returns the socket identitifers >where there has been some activity. Then we go thru each socket, retrieve >the context and deal with it. When all sockets have been dealed to, the event >loop continues. Under Unix, the same event loop is used to handle user >interface events. So this means that handling of events is serialized? That is, you don't have a pool of threads to process callbacks. So if the handling of the 3rd event will involve sending a another request, you won't be sending out that request until you get to that 3rd event. >> ----------------- >> I used a threaded debug utility to trace Netscape on Windows > >Just for curiosity, what's the name of that tool? :) Mutex bugtrapper. -mda
Received on Friday, 11 June 1999 15:40:15 UTC