[Cosmo-dev] Cosmo WebUI Service Layer

[Matthew Eernisse]

This is all good stuff. So far only one question occurs to me -- see below.

Ted Leung wrote:
>>>>> The MDC api is likely to be more stable, and I'd rather not have to 
>>>>> make the UI dev manually inject conduits into newly created 
>>>>> items/collections.
>>>> This will never be necessary, as the conduit injection will be done 
>>>> at the conduit level. Essentially, items will inherit the Conduit 
>>>> they were fetched over. I'll add  this to the proposal.
>>>
>>> So the Conduit will update a field in items that it fetches?
>>>
>>
>> What do you mean? If you mean that a conduit will stick it self in any 
>> item it fecthes, than yes.
> 
> Yes, that's what I meant.

Maybe I missed some explanation, but I don't see anything that addresses 
the question of an item that lives in multiple collections with 
different conduits (potentially with different levels of permissions).

Right now the UI code assumes read/write permission at the collection 
level, and users can only manipulate items in the currently selected 
collection -- so wouldn't it make sense to have the MDC methods use the 
conduit of the currently selected collection?

Although that also does raise the question of what happens later when 
the UI can overlay multiple collections -- some of which have different 
levels of permission, but also share items? Should the MCD 'save' (for 
example) try to find the conduit with the highest level of permissions 
for that item, or what? What would Chandler do (WWCD :)) in a case like 
that?

That's all I have so far. Excellent work, y'all.


Matthew