[
Lists Home |
Date Index |
Thread Index
]
- From: David Brownell <david-b@pacbell.net>
- To: Dave Winer <dave@userland.com>
- Date: Mon, 10 May 1999 22:10:24 -0700
HTTP supports both temporary and permanent redirection; pass the
appropriate response status and a "Location:" header field, and
the client reissues the request.
I agree with the person who said that mechanism should be used ...
it'll need to be supported anyway, no sense in having two client
side mechanisms to implement and debug (one of which is already
widely deployed).
On the server side, there's the question of how to flag that such
a redirection is needed. Different servers have different solutions
for that, and I suspect you're trying to avoid needing to spend
the effort in the server to see if it's needed. You implied there
was structural logic that could be applied to speed things up;
that's the approach I'd take, then!
- Dave
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
