Re: Anchors/Fragments ?
"Peter Lister, Cranfield Computer Centre" <P.Lister@cranfield.ac.uk>
Message-id: <9401241106.AA02151@xdm039.ccc.cranfield.ac.uk>
To: Liam Relihan <relihanl@ul.ie>
Cc: ccprl@cranfield.ac.uk, www-talk@www0.cern.ch
Subject: Re: Anchors/Fragments ?
In-reply-to: Your message of "Sun, 23 Jan 94 16:54:20 GMT." <Pine.3.05.9401231620.A15784-b100000@itdsrv1.ul.ie>
Date: Mon, 24 Jan 94 11:06:28 GMT
From: "Peter Lister, Cranfield Computer Centre" <P.Lister@cranfield.ac.uk>
Content-Length: 1245
I asked a connected question some time ago. The net.wisdom was that
'//fred/foo?bar' implies a query 'bar' sent to server 'fred' in the
context of path 'foo'; interpretation of 'bar' is up to fred, and the
browser is not expected to do anything special to the reply, other than
display it normally.
'//fred/foo#bar' means that the browser requests 'foo' from fred
(without mentioning 'bar'), and displays the reply in manner
illustrating the part of the reply marked 'bar' (e.g. an HTML anchor
with includes 'name="bar"' ).
Fragments (#) are interpreted by the browser, queries (?) by the
server. The difference is *not* semantic in terms of document
structure: a 'query' need not be a question per se, it could
semantically be a logical 'fragment'; equally, a 'fragment' could be
something more normally associated with a question, (e.g. if the reply
were a plain text file, the browser might insert a linked list of
anchors around each occurence of 'bar').
Peter Lister Email: p.lister@cranfield.ac.uk
Computer Centre, Cranfield University Voice: +44 234 754200 ext 2828
Cranfield, Bedfordshire MK43 0AL UK Fax: +44 234 750875
--- Widget. It's got a widget. A lovely widget. A widget it has got. ---