Re: [httpbis] #223: Allowing heuristic caching for new status codes

I'm in Changai airport right now, and not in any position to tweak.

The overall approach may be workable, but the thing that immediately leaps out at me is the new, magical semantics for public.  No cache behaves like that to my knowledge, and furthermore it's pretty useless; if an origin is going to go to the trouble to mark something public, it can assign an explicit freshness lifetime.

Please hold publication until we work through this; there's no sense in publishing two drafts in as many days. I'll be in Tokyo tomorrow and with any luck we can work through this reasonably quickly; might've worth it todo a quick Skype or FaceTime call. 

I'm genuinely surprised my iPad didn't autocorrect a trademark after FaceTime there. And iPad.

--
Mark Nottingham  http://www.mnot.net/

On 27/01/2013, at 6:50 PM, "httpbis" <trac+httpbis@trac.tools.ietf.org> wrote:

> #223: Allowing heuristic caching for new status codes
> -----------------------------+-----------------------------
>  Reporter:  mnot@pobox.com  |      Owner:
>      Type:  design          |     Status:  closed
>  Priority:  normal          |  Milestone:  22
> Component:  p6-cache        |   Severity:  In WG Last Call
> Resolution:  incorporated    |   Keywords:
>    Origin:                  |
> -----------------------------+-----------------------------
> Changes (by fielding@gbiv.com):
> 
> * status:  reopened => closed
> * resolution:   => incorporated
> 
> 
> Comment:
> 
> Since the above is mostly editorial (except for the bit about cache-
> control public allowing heuristics), I have gone ahead and committed so
> that we can close out the first WGLC comments. Feel free to tweak it if
> you disagree, or save it for a new issue during the next WGLC.
> 
> -- 
> Ticket URL: <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/223#comment:18>
> httpbis <http://tools.ietf.org/wg/httpbis/>
>

Received on Sunday, 27 January 2013 14:13:36 UTC