I'm still not sure what was the best implementation in TCustomWSocket.
Anything speaking against your timer-based code in HttpProt.pas?
Since W2K there are plenty of timers possible.
For cilent application, there should be no problem. But for a server
application with potentially hundreds or thousands of simultaneous users, a
solution with a single timer (whatever it is) would probably preserve system
resources. System resources is currently the main limiting factor in the
number of concurrent connections. This is why I designed TIcsWndControl in
the first place.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be