- From: Henrik Frystyk Nielsen <frystyk@w3.org>
- Date: Tue, 01 Sep 1998 17:38:48 -0400
- To: www-lib@w3.org
There has been some talk recently about how to time out stalled requests after a period of time. The hooks essentially were there but a few new features had to be added. The patch is described at http://db.w3.org/Library/latest.sql I have now committed an update that does support graceful timeout of requests. It is possible to set/change the timeout for all requests using these HTHost methods extern int HTHost_eventTimeout (void); extern void HTHost_setEventTimeout (int millis); defined in http://www.w3.org/Library/src/HTHost.html The default timeout in webbot and command line tool is 20 secs. Can be changed using the -timeout command line option. I have tested the patch on linux, solaris, and digital unix but not yet on Windows NT. Help doing this would be appreciated! At the same time, these changes were committed as well: a) Added support for etags in 201 responses. This will help avoiding the lost update problem when multiple people are editing the same document. b) Fixed a problem that prevented idle connections to be closed after 60 secs idle time. This functionality was there but because of a chance some in a related place, it didn't execute as designed. Client side closes are a lot easier to deal with as we don't get in to nasty recover resets of pipelined requests. c) Expanded progress flags in HTAlert to be 32 bit instead of 16 bit as I was running out of flags. I don't think this affects anybody except from people working on 16 bit machines. Btw, it would be nice to hear whether anybody are working on 16 bit ports and what their status is. Please try out these updates and see how they work. Have fun! Henrik -- Henrik Frystyk Nielsen, World Wide Web Consortium http://www.w3.org/People/Frystyk
Received on Tuesday, 1 September 1998 17:38:25 UTC