Hello Cliff and thank you for the reply
Since I skipped the usual "hello first post" let me just say here that I just love all that PureMVC is right now. Great code, great docs, great feedback.
Now regarding the problem at hand:
The API is REST it allows a pretty good separation of projects logic and todos logic for instance. Each todoList has it's own id and u can CRUD it just using that. Well for the C part u need the project id
Thinking about this yesterday it's quite clear that the server side already incorporates a great deal of domain logic so the inter proxy comm would mostly be "hey, I changed a bit here and here so u might need to update yourself".
While keeping the array of TodoListVO s as a property of a ProjectVO (project hasMany lists) is natural this might become a problem for more complex data relations. So I think that if the proxies can talk one to the other then I will make each handle one of the data types.
Hmm, right now it's obvious that I'm thinking of the Proxy as a DB table Proxy. Does this seem flawed to anyone?
Well not really a DB table proxy. More a data type proxy. Which should fit the model idea. I think. I won't have a proxy for a table that holds the project types...
Regarding a proxy for each of the project's TodoLists.
How would I manage the creation of many proxies? How does the framework help with the factory thingy. Would this be a job for the ProjectsProxy?
cosmin