W3C home > Mailing lists > Public > www-lib@w3.org > October to December 1996

Re: (?) Multiple concurrent requests for the same anchor.

From: <neumann@nestroy.wi-inf.uni-essen.de>
Date: Tue Dec 17 07:12:38 1996
Message-Id: <9612171211.AA22566@nestroy.wi-inf.uni-essen.de>
To: qinglong@Yggdrasil.com
Cc: www-lib@w3.org
In your message from [Tue, 17 Dec 1996 14:58:57 +0300 (MSK)] you wrote:
: > 	HTRequest_setReloadMode(obj->request, HT_CACHE_FLUSH);
: [...]
: > Hopefully, that CACHE_FLUSH disables the check for anchor document in
: > memory cache filter when I really want to start a new load operation.
:                                                     ^^^^^^^^
:    This is the main problem.
 ...
:    And I want to get informed in some way, if the anchor is currently being
:  loaded (a request for the anchor has been issued, but not finished yet).
:  If this is the case, starting a new load (and even reload) operation
:  would be unreasonable --- the document which is currently being loaded
:  is fresh and that's why it's the best variant.

 We do shuch a thing with libwww 5.0a in the cineast browser. We have
 there a class called "RequestManager" which keeps track of the current
 running requests (i.e. ansynchronosly loading requests). whenever a 
 new request is announced it checks whether this anchor is currently
 being obtained. If so, that latter request "joins" the earlier request.
 whenever data (or eof or an exception) arrives all parties of a joined requests 
 can be informed.

 We do this in MIT OTcl, keeping associative array is very simple there.
 
 -gustaf
--
Wirtschaftsinformatik und Softwaretechnik        
Universitaet GH Essen, FB5
Altendorfer Strasse 97-101, Eingang B, D-45143 Essen
Tel.: +49 (0201) 81003-74, Fax:  +49 (0201) 81003-73
Gustaf.Neumann@uni-essen.de
http://mohegan.wi-inf.uni-essen.de/Neumann.html
Received on Tuesday, 17 December 1996 07:12:38 GMT

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