Is HTHost_forceFlush supposed to permanently reset host->forceWriteFlush? From the name and use, I wouldn't expect that behavior. (Called from HTTP_CONNECTED label in HTTP.c after some kind of pipe error condition which I haven't figured out; sets value to NO, resulting in delayed flushes from then on) RCS file: /sources/public/libwww/Library/src/HTHost.c,v retrieving revision 2.68 PUBLIC int HTHost_forceFlush(HTHost * host) { HTNet * targetNet = (HTNet *) HTList_lastObject(host->pipeline); int ret; if (targetNet == NULL) return HT_ERROR; HTTRACE(CORE_TRACE, "Host Event.. FLUSH passed to `%s\'\n" _ HTAnchor_physical(HTRequest_anchor(HTNet_request(targetNet)))); host->forceWriteFlush = YES; ret = (*targetNet->event.cbf)(HTChannel_socket(host->channel), targetNet->event.param, HTEvent_FLUSH); host->forceWriteFlush = NO; ^^^^^^^^^^^^^^^Received on Thursday, 11 May 2000 12:03:18 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:36 GMT