Hi, I am encountering several questions syncing calendar with Nokia 7210c,
please be patient,;-)

1. Shall I use legacy mode? Since 7210c only supports vcalendar 1.0 (It does
not accept ical content type via SAN and it sends messages in vcal1.0
format, so I assume this.) I just skimmed the sample configuraiton in
syncserver_sample.xml and found some remote rule configuraitons for various
phones, but did not see explict use of legacy mode. Have I made something
wrong?

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?
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?

3. TZ property is only declared in VCalendar profile, while the particular
phone sends it within vEvent subprofile, so I added the following to our
configuration:
         <subprofile name="VEVENT" nummandatory="1" showifselectedonly="yes" 
field="ISEVENT" value="1">
 
+            <property onlyformode="old" name="TZ" filter="false" 
suppressempty="yes">
+                <value field="DTSTART" conversion="tz"/>
+            </property>

Yes, it is non-standard compliant. So can I have a specific profile for this
particular phone?

4. STATUS property maybe used directly instead of as a parameter for ATTANDEE
property inside vEvent profile (This is vcal1.0 explictly states). So I will
add this declarion in vEvent subprofile. At this moment it parsed correctly,
however when it starts to store to datastore (during beforewrotescript), it
still losts the STATUS, I am checking on this at the moment.

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?

see example:
This is what local datastore is:
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
BEGIN:VEVENT
SUMMARY:phone meeting
DTEND:20060406T163000Z
DTSTART:20060406T160000Z
DTSTAMP:20060406T211449Z
LOCATION:my office
DESCRIPTION:let's talk<<REVISION>>
UID:20091202t070241z-12684-1000-...@shlabwcchen35
CREATED:20091202T070241Z
LAST-MODIFIED:20091202T070241Z
END:VEVENT
END:VCALENDAR

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
-- 
Regards,

Chen Congwu
Moblin China Development


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

Reply via email to