> -----Original Message-----
> From: Michael Richardson <mcr+i...@sandelman.ca>
> Sent: Friday, February 22, 2019 8:46 AM
> To: Carsten Bormann <c...@tzi.org>
> Cc: Jim Schaad <i...@augustcellars.com>; Panos Kampanakis (pkampana)
> <pkamp...@cisco.com>; ace <ace@ietf.org>; Klaus Hartke
> <har...@projectcool.de>; draft-ietf-ace-coap-...@ietf.org
> Subject: Re: [Ace] Embedded Content Types
>
>
> Carsten Bormann <c...@tzi.org> wrote:
> >> I am thinking of two different URLs, that is not do the difference
by
> >> a query parameter but by changing the URI.
>
> > Note that the query parameters are part of the URI, so fundamentally
> > there is no difference between putting the info there or in the path
> > part of the URI.
>
> Really? Aren't there caching differences?
> (Not that these things should ever be cached)
Not in CoAP, for CoAP options are part of the cache key. I don't know for
sure about HTTP but normally it says only GETs and use the URI. That would
say that options are part of the cache key.
Jim
>
> --
> Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
>
>
_______________________________________________
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
