On Wednesday 15 August 2012 03:01 AM, Glyph wrote:
Yes. Look at the TimezoneService plist entry (have a look at stdconfig.py for the closest thing to documentation on that option ;-). You need to set the server as a "secondary" rather than a "primary" (the default), and set TimezoneService.SecondaryService.Host / .URI to another timezone service that implements this draft specification. We have done interop testing on other Calendar Server instances, DAViCal <http://davical.org>, and Bedework <http://www.jasig.org/bedework>. -glyph
I looked around for any public servers that provided the timezone service. I couldn't find any such service. Anyways, I think the former option of updating the calendarserver timezone database is the better way to handle this situation. Thanks for providing the instructions in the wiki page. I will look into it sometime soon.
Regards, Rahul. _______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-dev
