I am thinking this leads to a pattern like this:
- I need to work with persons, so I fetch a list of them from a remote service.
- I choose to work with the person with id "3";
- present the contacts of person "3". (here is the tricky stuff, all the contacts that I load have a reference to person "3", what do I do about that? do I re fetch it, creating a different object and breaking uniquing, or do I look for a way to prevent that "same but different object" in my application? )
But... until granite has that... what could we do as a first step? it would be nice if we could "merge" a recently obtained object with one a fetched before... something like ADO.NET DataSet... (I can not believe I am writing that I miss the DataSet)
I guess that until Granite has his own "Data Management" the way to handle data will be... to imitate the practices of traditional AJAX applications?