Re: Is it correct to respond with partial representation for low capabilities media-types?

Hi Philippe,

On Jun 20, 2012, at 1:09 AM, Philippe Rathé wrote:

> 
> > Looking a the application the client intends to create (the use case realized by the user agent) is not an option because in a RESTful system the server does not (and must not) know the application the client is trying to walk through.
> 
> I guess that it comes from the stateless constraint?

Erm, no :-) That would be the hypermedia constraint.

> 
> > All the server developer really has is the media type spec of the media type it is going to serve.
> 
> There is also rfc5988 which provides link relations "outside" a media-types.

Yep - sorry. I keep summing this up under 'media type'. And continue to get beaten up for it :-)

> 
> > The solution to the 'problem' is that the server developer's task is not to implement something useless, but to expose the capabilities of the server side component in a way that provides a benefit to the client, in a way that is useful. You could add: in a way that maximizes re-usability.
> 
> I have face limitations when thinking of re-usability. My first
> reaction is to modified my original ideas by bowing to what the
> standards and protocol can do well for me. But that is a matter of
> philosophy.
> 

And a matter of being interested in long-term benefits. Not many people are ... and sometimes rightly so :-)


Jan

> --Philippe
> 



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rest-discuss/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rest-discuss/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/