More on the Restful Objects spec
Resources and Representations
Been continuing to work on the Restful Objects spec, which aims to defines a set of RESTful resources, and corresponding JSON representations, for accessing and manipulating a domain object model.
I’ve just uploaded the current draft (v0.22) up to the Restful Objects site. There have been numerous changes since the last version, not least of which is the set of resources that it defines (see left).
Another change is that the spec now explicitly indicates that it is agnostic as to the nature of the server-side state that it exposes, in that it may be used either to expose domain entities (Customer, Order, Product) or may be used to expose use cases/commands (CheckIntoFlight, CancelOrder). So, irrespective of which view you have of how to do REST, Restful Objects aims to provide useful support.
Anyway, if any of this sounds of interest, head over to the Restful Objects site to download the latest version of the spec.
Posted on September 4, 2011, in Uncategorized and tagged restful objects. Bookmark the permalink. 2 Comments.
Is this really a good idea, surely the years spent on Corba/RPC against objects showed us that its not possible for a domain model to provide a good service API?
Even if it was for non-trivial cases its just another responsibility for your domain objects, and to me they usually have enough to do already.
Colin,
Thanks for taking the time to reply.
I don’t think that RO spec is attempting to reinvent corba; it’s certainly not its intent! Rather than repeat myself, let me refer on to the comments – most specifically with regards to media types – in the comments to the follow-on post.
Thx
Dan