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

(?) Multiple concurrent requests for the same anchor.

From: Markku Savela <msa@msa.tte.vtt.fi>
Date: Tue, 17 Dec 1996 13:09:51 +0200 (EET)
Message-Id: <199612171109.NAA04564@msa.tte.vtt.fi>
To: qinglong@Yggdrasil.com
CC: www-lib@w3.org

> My question is whether there is some standard way to find out if the
> given anchor is already being loaded (there is a request for it)?
> If someone issues a request for the anchor, which is already being
> loaded, it will duplicate the loading and so on...

I *am* using the document (HTAnchor_setDocument) for this purpose.

> ... Memory cache before filter
> (HTMemoryCacheFilter) checks if the anchor has (non NULL) document in it,
> and uses this as a sign of the anchor already has been requested and
> loaded, ...

Maybe I am just lucky and my application works with current library
(5.0a) and breaks with the next version, or perhaps the following
piece of code (copied from some examples) helps me?

	HTRequest_setReloadMode(obj->request, HT_CACHE_FLUSH);
	if (!HTLoadAnchor((HTAnchor *)obj->anchor, obj->request))
		...
		...

Hopefully, that CACHE_FLUSH disables the check for anchor document in
memory cache filter when I really want to start a new load operation.

--
Markku Savela (msa@hemuli.tte.vtt.fi),     Technical Research Centre of Finland
Multimedia Systems, P.O.Box 1203,FIN-02044 VTT,http://www.vtt.fi/tte/staff/msa/
Received on Tuesday, 17 December 1996 06:10:36 GMT

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