On Sep 17, 2009, at 9:25 AM, Felipe Gaúcho wrote:
>> Do not get yourself into the trap of thinking that the URI of a
>> resource should be a column in a database table.
>
> Dont't need to be a column, but in my case it will be a "placeholder"
> column since my Entities are also my serializable elements.. I will
> just not care what the content is in the database (a collection 1..n)
> but the column should be there (in my specific architecture) to allow
> the serialization of the entities without tricks in the service
> layer....
>
>> terms, the URI of a resource is a *view* tier concept, not a
>> *model* tier
>
> About model X view: in hateoas, the idea is that the service guide the
> client through its navigation.. a bit weird concept and I am yet not
> sure about its applicability in the real world..
The Web is built on it, it is how browsers know when you click on a
link that a GET should be performed, or that a POST should be
performed with certain parameters,
The key for machine processable hypermedia is to associate semantic
information with the link, typed links if you like so that client
knows what to do with the link. Sometimes the media type is
sufficient, forms, sometimes micro-formats can work in (X)HTML, or a
"rel" attribute.
Paul
> but what I am doing
> right now is to include the next-possible-states or
> the-most-natural-next-steps in the resources.. so the Client should
> find quickly the URLs it need to navigate through the application....
>
> It is the first time I am designing software with hateoas in mind, and
> I am sure I will mature this concept during the next few months/years
> until to have a set comfortable and robust architecture skills on
> this.. but for now it is a lot of fun learning :)
>
> nice chat .. let's see the evolution of this..
>
> all code is public, and as soon I have my first results I plan to blog
> or at least to discuss here my design decisions.......
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>