On Wed, 2009-12-02 at 07:50 +0000, Chen Congwu wrote:
> 2. Shall we (SyncEvolution) merge the remote rule configurations for
> various phones already done by synthesis, so that we can benefit
> immediately from synthesis excellent work. And of course we will
> contribute back our new findings. So we need to setup a similar syncing
> approach for configuration files for server case just like what we are
> doing for client configurations?

Absolutely. There's an open issue (#7712) and in one of my recent mails
to this list (Subject: "merging branches + XML config tracking") I
brought up the same question.

> To Patrick, do we need to seperate the server and client configurations just
> like synthesis or stick to the combined approach we used at the moment?

See that email - I would prefer separate files, plus a mechanism in
SyncEvolution to gather them into one XML config at runtime.

> 5. For clients which do not support UTC time (common case for phones?), we 
> will
> send the time as localtime (not floating time? Does it mean vcal1.0 does not
> have such a concept?). However we did not sent the TZ field to client, how can
> the client correctly interprect this?
[...]
> This is what we sent:
> BEGIN:VCALENDAR
> VERSION:1.0
> BEGIN:VEVENT
> SUMMARY:phone meeting
> DESCRIPTION:let's talk<<REVISION>>
> LOCATION:my office
> DTSTART:20060407T000000
> DTEND:20060407T003000
> END:VEVENT
> END:VCALENDAR

The server needs to know (or guess) what the local time zone of the
phone is and convert all time stamps into that zone. Yes, this is error
prone. Yes, it can break for recurring events in "foreign" time zones.
Stupid phones.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis

Reply via email to