- ... Hi Jorn, In this example the shared understanding is really coming from the link relations. Link relations can exist independently from the media type,Message 1 of 245 , Jan 3, 2012View Source
On 3 January 2012 13:07, Jorn Wildt <jw@...> wrote:Yes.> The critical point is how the shared understanding between client and
> server is achieved, and whether the "network-visible" semantic is
> sufficient for the shared understanding.
> Let's have a resource, which accepts "image/png" on POST and does
> certain image processing, returning a resource URI, where the
> generated image could be retrieved.
I would say the link-reltype that points to the page that accepts the POST.> How does the client decides where to send the POST command, if it
> wants a specific type of image processing? Out-of-band information
The link-reltypes would be documented in the media-type spec.
It could go like this:
1) Client GETs image processing descriptor resource.
2) Server returns media-type "application/vnd.imageprocessor+xml". Now the client has a shared understanding with server about the server's capabilities.
3) The client selects a proper link from the response using link-reltypes documented in the media-type spec.
4) Client POSTs image to the selected URL.
All-in-all ... the shared understanding comes from the media-type.Hi Jorn,In this example the shared understanding is really coming from the link relations. Link relations can exist independently from the media type, which is how shared understanding is established when using generic (hyper)media types.Cheers,Mike
- ... The way i read that post, message type is a way for the client to inform the server how it has decided to use a particular link. Not a way for the serverMessage 245 of 245 , Jan 12, 2012View SourceOn Wed, Jan 11, 2012 at 1:44 PM, Darrel Miller <darrel.miller@...> wrote:
> In thisThe way i read that post, message type is a way for the client to
> post http://old.nabble.com/Re%3A-Unifying---standardizing-X-Moz---X-Purpose-headers-p29794338.html%c2%a0Roy
> talks about the notion of passive links in Waka. Without putting works into
> Roy's mouth, this is what I consider to be a LE.
inform the server how it has decided to use a particular link. Not a
way for the server to tell the client how it should use a particular
link. Ie, it would be ok for a client to dereference a `img` tag link
as an active request (or any other valid value, for that matter).