[Chandler-dev] Checking background sync into the trunk [Poll]

[Philippe Bossut]

I understand that "stamping of shared items" won't work but will 
"sharing of stamped items" will? I do have quite a bit of those and, if 
I can't use sync for a while because of that, I'd like to know.

BTW, the office shared calendar does contain events that are stamped as 
email (done when sending invites). Does this means we won't be able to 
sync the Office calendar?

Cheers,
- Philippe

Morgen Sagen wrote:
>
> On Jun 6, 2006, at 5:31 PM, Katie Capps Parlante wrote:
>
>> I'm in favor of #1
>>    + background sync is currently our highest priority for alpha3
>>    + we've found so far that finding the bugs and making reproducible 
>> test cases to be the time consuming part, and fixing bugs goes more 
>> quickly, so I'd like to see us invest more time as a team in finding 
>> bugs
>>    + if we shake out problems earlier we can make a better assessment 
>> for the schedule, which helps with other planning decisions
>>
>> Morgen, could you elaborate on the consequences of stamping/sharing 
>> not working correctly in the interim? Does it fail gracefully?
>
> At the moment, it's not quite graceful: the sidebar would indicate an 
> error (via the exclamation icon), a stack trace would appear in 
> chandler.log, but each sync of that collection would fail (although 
> other collections would not be affected -- they would continue to 
> sync).  I'm currently looking at how to better recover from this 
> state, aside from deleting the local collection and re-subscribing.
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev