Lists Home |
Date Index |
- To: firstname.lastname@example.org
- Subject: how is xpointer supposed to work?
- From: Stefano Debenedetti <email@example.com>
- Date: Thu, 07 Nov 2002 16:19:50 +0100
- Carmen-published-at: <http://webaccess.mozquito.com:8080/mail/ste/outbox/1052642173193068920.xml>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
it is very unclear to me how is XPointer information to be received by an XPointer-enabled server, and if such a server is even supposed to exist, as it seems to me that existing browsers keep any info after the crosshatch char # for after-resource-retrieval processing and don't send that part of the URL to the server, and from what I gaher that happens to be conformant to RFC 2396, is that true?
What am I missing here? Is XPointer supposed to work only if different clients become available? (i.e. browsers that process XPointer or that send the pointer part to the server)
Hope someone can help understand this, thanks