Well, in fact I learned the existence of the anchor attribute from studying
the Link RFC... I think this answers your question. The anchor attribute is
exactly made for solving that issue, and to prevent people like us from
reinventing the wheel.
> -----Original Message-----
> From: Bill Burke [mailto:bburke_at_redhat.com]
> Sent: Mittwoch, 21. Dezember 2011 20:43
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: Using "anchor" attribute of "Link" header
>
>
>
> On 12/21/11 2:15 PM, Santiago Pericas-Geertsen wrote:
> >> </cluster>; anchor="machine/gamma/stopper";
> >> produces="application/json"; method="POST";rel="stopper"
> >
> > This proposal I'm not thrilled about. I find this use of the anchor
> > non-intuitive (as well as more difficult to process), even more so
> > than the link templates on the wiki. Again, the current API will
> allow
> > you to create such a link, but it won't be processable by
> > Client.invocation() --yet you could still use Client.target(.) and
> > build your request from there.
> >
> > So -1 on #2, but I'm curious what other experts think about it?
> >
>
> Is anchor even part of the link header spec? I don't remember it being
> in there.
>
> Bill
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com