[Design] [Cosmo][Desktop] Making sure the server never ends up with a big pile of untriaged Chandler items

[Morgen Sagen]

On May 31, 2007, at 12:25 PM, Mimi Yin wrote:

> Oh okay. That seems like a reasonable strategy. Morgen?
>
> On May 31, 2007, at 12:14 PM, Jeffrey Harris wrote:
>
>> Hi Folks,
>>
>>> I think all of this depends on just how slow the web UI will be  
>>> if it
>>> has to load all the items, untriaged.
>>>
>>> Mimi
>>
>> Could we hold off on removing the don't-share-triage-status option  
>> from
>> subscribe?  Now that we've loosely decided the web UI will process
>> not-yet-triaged items, it seems like there wouldn't be much harm in
>> holding off on waiting and seeing what the experience is like in  
>> the web UI.
>>
>> Sincerely,
>> Jeffrey
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Design" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/design
>

Just to be clear, we're talking about the "publish" dialog, and I am  
more than willing to wait until later to address this in Chandler.  I  
still contend this is going to be a problem for collections that non- 
Chandler CalDAV clients publish, so it has to be addressed on the  
Cosmo/WebUI end at some point anyway, unless other CalDAV clients are  
not going to be supported by Cosmo.