Replying inline. On Sun, Jun 17, 2012 at 4:49 AM, Dan Haywood <[email protected]> wrote: > On 16 June 2012 04:06, Adam Howard <[email protected]> wrote: >>... On subsequent requests for the object, it is ALWAYS >> refreshed from the server including all of its relations. So the >> cache is really just used to ensure that all current views are in >> sync with each other...
> in which case, sounds like a decent design. I'd keep with it. I like the design too. I'm hoping Johan replies and I can move forward with his code. It also sounds like cache is not the right word for it. I'll have to go back and find the right CS term for this. It sounds like the real caching will be handled with the standard HTTP mechanisms. I like that too. The javascript can always ask for what it wants and the caching (a purely performance concern) is handled transparently. Thanks for the pointers to the appropriate RO spec sections. I'll read it over again now that it's reached 1.0.0. Speaking of that, is there any way I can help get the json-viewer updated? For example, I'd like the rel="iconName" link included so I can show custom icons instead of the generic buttons for services. Could I write this up and submit a jira ticket with a patch? -- Adam Howard
