W3C home > Mailing lists > Public > public-rdf-wg@w3.org > January 2012

Re: mitigating cost of 303

From: David Wood <david@3roundstones.com>
Date: Wed, 4 Jan 2012 08:59:59 -0500
Cc: Steve Harris <steve.harris@garlik.com>, "public-rdf-wg@w3.org" <public-rdf-wg@w3.org>
Message-Id: <D5269007-EB3A-4A91-A354-C61B6E8E26DF@3roundstones.com>
To: Sandro Hawke <sandro@w3.org>
On Jan 3, 2012, at 20:59, Sandro Hawke wrote:

> On Thu, 2011-12-22 at 13:37 +0000, Steve Harris wrote:
>> FWIW I agree with him that a 303 is a very high cost to pay.
> In confusion or in extra round-trips?
> I have an engineering solution to the latter, which is that hosts be
> allowed to expose (via a .well-known URI) some of the rewrite rules they
> use.   Then, if I (as a client) find myself getting lots of redirects
> from a host, I could look for this redirect-info file, and if it
> appears, I can do the redirects in the client, without talking to the
> server.   
> This wouldn't be only for RDF, but I'd expect only people doing 303 to
> care enough to set this up on their hosts or have their clients look for
> it.
> The hardest engineering part, I think, is figuring out how to encode the
> rewrite rules.  

Weren't you the editor of RIF in RDF [1]?


[1] http://www.w3.org/2005/rules/wiki/RIF_In_RDF

> Each server has its own fancy way of doing it.  Like
> which version of regexps, and how to extract from the pattern space;
> lots of solutions, but we'd need to pick one.   And, tool wise, one
> would eventually like the web servers to automatically serve this file
> based on the rewrite rules they are actually using.   :-)
>   -- Sandro
Received on Wednesday, 4 January 2012 14:03:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:02 UTC