W3C home > Mailing lists > Public > uri@w3.org > April 2003

fragment identifiers applied before entire content is retrieved

From: Larry Masinter <LMM@acm.org>
Date: Thu, 17 Apr 2003 00:17:40 -0700
To: <uri@w3.org>
Message-ID: <000401c304b1$6f373f40$6ace8642@MASINTERPAD>

During the discussion of temporal fragment identifiers,
I've noted that some of the wording in RFC 2396 might
need some minor tweaking:

    When a URI reference is used to perform a retrieval action on the
    identified resource, the optional fragment identifier, separated
from
    the URI by a crosshatch ("#") character, consists of additional
    reference information to be interpreted by the user agent after the
    retrieval action has been successfully completed.  ....

The fragment identifier can be interpreted by the user agent
before "the retrieval action has been successfully completed"
but after it's been successfully initiated. For example,
in HTML pages, the browser can scroll to the identified
fragment as soon as it's been parsed, and not wait until
the _entire_ document has been retrieved.

Similarly, if you open a PDF file with a page identifier
   http://acroeng.adobe.com/BrowserTestSuite/auxurl/auxurl_testpage.html
it doesn't need to download the entire file before it can turn
to the appropriate page, using byte range retrieval.
Received on Thursday, 17 April 2003 03:17:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:31 GMT