Re: [Chandler-dev] Shared triage status for rearchitecture

Hi Jeffrey,

I think if you're sharing Triage Status, everyone should see the same  
Triage Status.
However, we could get around this by tying Alarms and Triage Status.

Mimi

On Sep 24, 2008, at 10:59 AM, Jeffrey Harris wrote:

> Hi Mimi,
>
>> How would not syncing auto-stuff affect the web UI?
>
> It would mean the web UI wouldn't look right (unless or until we  
> updated
> the web UI).
>
>> If I set an alarm to tickle a note to NOW. Would the web UI still  
>> show
>> that the item had tickled to NOW, even though it doesn't have a  
>> notion
>> of tickling? Would we need to implement the auto-triage  
>> functionality on
>> the web UI to keep things in sync?
>
> Yes, to the extent that we put effort into maintaining the same  
> view of
> data between web UI and desktop implementations, the web UI would need
> to include alarms in its calculations, and we might need to do some
> slightly different stuff with triage status in general.
>
>> There is also the scenario of 2 desktop clients that are sharing  
>> Triage
>> Status, but not alarms. If Desktop 1 fires an alarm and tickles  
>> the item
>> to NOW, would Desktop 2 see the item as NOW even though Desktop 2's
>> alarm hadn't fired yet?
>
> They'd see different things.  It's not clear to me that's actually  
> a bad
> outcome, though.
>
> Sincerely,
> Jeffrey

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev