Hi Roy,
On Thu, May 21, 2015 at 11:59 PM, Roy Fielding wrote:
> If your application sends messages outside its own memory space, X- is not
> appropriate for
> those fields
Would not that be the case for all headers i.e. as it involves remote
communication.
If using X-Sling-Tracer is not approp
> On May 21, 2015, at 1:40 AM, Chetan Mehrotra
> wrote:
>
> Repeating my answer on the other thread
>
> ===
> That recommendation is meant for headers which are
> meant to be used in a wider context. Header which are very much
> specific to application are better prefixed to indicate that they
Repeating my answer on the other thread
===
That recommendation is meant for headers which are
meant to be used in a wider context. Header which are very much
specific to application are better prefixed to indicate that they are
custom ones IMHO [2]. So I would prefer naming them X-Sling-Tracers.
Hi,
On Thu, May 21, 2015 at 10:30 AM, Robert Munteanu wrote:
> ...the X- prefix is deprecated with RFC6648 [1]..
Interesting, so IIUC the plan is just to use our own prefix like
Sling- for custom headers, and hope for the best?
-Bertrand
> [1]: http://tools.ietf.org/html/rfc6648
