RE: Announcement: "Cool URIs for the Semantic Web" - W3C SWEO IG Note

> From: Peter Ansell
> [ . . . ]
> I always thought 303 redirects were not cacheable... "The 303 response
>  MUST NOT be cached, but the response to the second (redirected)
>  request might be cacheable"[1]
> [ . . . ]
>  [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.4

True, but all that really means in practice is that a client must not assume that the server response at time t+1 will be the same as it was at time t.  But if the client is a SWeb application, does it really care whether the response might be different at a slightly later time t+1?  Probably not.  It will probably be perfectly content using the data it got at time t.  In fact, to avoid inconsistency, most SWeb applications probably would *prefer* to repeatedly use the same time t data during a single program execution, rather than use some data from time t and some from time t+1, in case the server was in the process of updating the data.


David Booth, Ph.D.
HP Software
+1 617 629 8881 office  |  dbooth@hp.com
http://www.hp.com/go/software

Opinions expressed herein are those of the author and do not represent the official views of HP unless explicitly stated otherwise.

Received on Wednesday, 9 April 2008 19:53:09 UTC