By way of background, see section 34.4 of the RO spec 1.0.
After some exploration of possibilities, and further discussion with Dan, we have taken the following decisions:
- We are now referring to this capability as 'eager rendering' - meaning that more information will rendered in the representation returned by the RO server to the client. Ideally, for efficiency, this will also trigger 'eager loading' (meaning, eager loading
of data from database to the server), but this is a separate point - and there could be circumstances where you want eager loading from the database without any eager rendering to the client.
- Rather than implement the 'x-ro-follow-links' query param as proposed in the spec (which is fairly complex), our initial support for eager rendering will be via a new
[Eager] (or possibly [Eagerly]) attribute in the domain model. This can be applied to individual properties, actions, or a whole class (meaning that it then applies to all properties and actions.
- Although initially recognised only by the Restful Objects server, the intent is that this attribute would later apply to Naked Objects MVC also - meaning that the Html pages would have more info rendered in them.