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

(?) Multiple concurrent requests for the same anchor.

From: QingLong <qinglong@Bolizm.ihep.su>
Date: Tue, 17 Dec 1996 13:25:06 +0300 (MSK)
Message-ID: <961217w2.QLm11679@Bolizm.Yggdrasil.com>
To: www-lib@w3.org

	Hello!

   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...

   HTParentAnchor strcuture appears to have no member for this purpose,
 nor there is such a function in Anchor class. 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,
 so this can't be used by application to mark an anchor as being requested
 (if else HTMemory CacheFilter will return HT_LOADED and the document
 will not be actually got). But if the anchor has no content (document),
 an application cannot place any application specific information in it.
 Then how must it mark (or find out using WWW library API) an anchor as
 being already requested (some kind of anchor request locking)?

    Please, answer me. You can just say ``Yes'' or ``No''.
 (``yes, such standard way exists'' vs ``no, this is an application business
    to maintain such info'').

    Thank You very much.
	       QingLong.

--
      QingLong                  Yggdrasil Computing, Incorporated
   +1 408 261-6630             "Free Software For The Rest of Us."
Received on Tuesday, 17 December 1996 05:15:33 GMT

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