On Feb 11, 2010, at 10:01 AM, Paul Sandoz wrote:
>
> On Feb 10, 2010, at 11:26 PM, Jan Algermissen wrote:
>
>>
>> On Feb 10, 2010, at 10:31 PM, Paul Sandoz wrote:
>>
>>>> (But then, I find the whole aproach to hypermedia confusing (sorry)).
>>>>
>>>
>>>
>>> I think in essence hypermedia is very elegant and once grasped surprisingly simple, but gosh it can take time to get your brain thinking the right way about it, well it did for me :-)
>>
>>
>> :-) I meant that I find the *Jersey approach* confusing!
>>
>
> As i suggested, if you have time, try playing with the example a bit :-)
Yep, just doing that.
Question: how are the return codes handled? E.g. upon POST /order/1/review
200 ok -> request succeeded with content - how s that content handled?
204 No Content -> easy: request succeeded
205 Reset Content -> any significance to this one or just handled like 204?
201 Created -> How does the framework react upon newly created resource?
Can I configure the client to proceed to GET the Location URI?
202 Accepted -> (I find this to be the most likely one) How does the
framework support the subsequent polling to check if request has
actually been processed
303 See Other -> Common pattern would be that the server uses this code to
redirect the client to the updated order. Is there support for this?
Jan
>
> Paul.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
-----------------------------------
Jan Algermissen, Consultant
NORD Software Consulting
Mail: algermissen_at_acm.org
Blog:
http://www.nordsc.com/blog/
Work:
http://www.nordsc.com/
-----------------------------------