RE: Issue: JW7 (redirects)

In many cases a search arbiter may not how the full response to a search
query but may know where to redirect the searcher to find them. So you could
make a single query to the search arbiter, get back some responses and also
get back an instruction that you should repeat the search at 4 other places
in order to get the full response. This is often an easier solution to
deploy, especially from a security point of view, then trying to have the
search arbiter call up the 4 other places, get the data and pass it along to
the user.

So there is a very strong need for this feature.

That doesn't mean it needs to go into V1.

		"The spec is done when there is nothing left to cut."
					Yaron

> -----Original Message-----
> From: Jim Davis [mailto:jdavis@coursenet.com]
> Sent: Mon, June 07, 1999 3:19 PM
> To: www-webdav-dasl@w3.org
> Subject: Issue: JW7 (redirects)
> 
> 
> See http://www.webdav.org/dasl/protocol/issues.html
> 
> Jim Whitehead asks whether a SEARCH can return a Redirect 
> reply, and if so,
> why then we need to support search arbiter redirection?
> 
> I propose:
> 
> 1. Yes, SEARCH can return a Redirect reply
> 2. Get rid of search arbiter redirection
> 
> It makes sense to support Redirect in any case.  (Most WebDAV 
> methods work
> with redirect, so why not SEARCH?)
> 
> Once you have Redirect, the only thing that search arbiter redirection
> gives you is the ability to return more than one alternative. 
>  This is not
> worth the additional effort and complexity.  We should strive 
> to make DASL
> as small as possible.  In particular, note that it's no use 
> to specify a
> feature unless there will likely be at least two interoperating
> implementations that use it.  I don't think this feature is 
> worthy of the
> spec.  The less we put in the spec, the quicker the review 
> process will be.
> 
> Therefore lets remove search redirection
> 
>

Received on Monday, 7 June 1999 18:32:07 UTC