[
Lists Home |
Date Index |
Thread Index
]
Well, yeah, the Fragment Identifier doesn't get sent to the HTTP Server.
When I said "send a request for a fragment identifier" I meant I'm sending
it from the user or application to the user agent, not to the server. So
typing a URI with a fragment on it is "sending a request" for it. My fingers
are sending the request (via the keyboard and windowing system) to the Web
Browser.
-Wayne Steele
>From: Eric van der Vlist <vdv@dyomedea.com>
>To: Rick Jelliffe <ricko@allette.com.au>
>CC: xml-dev@lists.xml.org
>Subject: Re: [xml-dev] XPointer and XML Schema
>Date: 18 Jul 2002 14:44:26 +0200
>
>On Thu, 2002-07-18 at 07:27, Rick Jelliffe wrote:
>
> > If I send a request for a fragment of a document,
>
>I think that this is where I don't understand any longer (maybe because
>of bad habits taken admnistrating web servers).
>
>Unless I am very wrong, in HTTP [1] there is no such thing as a fragment
>identifier: the client sends a HTTP request for a resource, gets this
>resource back and processes the document to find the fragment matching
>the fragment identifier.
>
>In other words, a client never sends a request for a fragment!
>
>And if the processing involves a PSVI, the PSVI has to be constructed
>client side with eventually no indication at all in the document (unless
>the server sends the PSVI but this would require defining a
>serialization for the PSVI first :-))))))...
>
>[1] ftp://ftp.isi.edu/in-notes/rfc2616.txt
>
>Eric
>--
>See you in San Diego.
> http://conferences.oreillynet.com/os2002/
>------------------------------------------------------------------------
>Eric van der Vlist http://xmlfr.org http://dyomedea.com
>(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
,
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
|
