Frank Mantek wrote: > "In theory, theory and practice are the same. In practice, they're not." > /--Yogi Berra/ > > I hear you... For us, there is a difference between offering platform > services that allow you to build "secure" systems that a customer can > trust (not to state that they can not trust you or your current > implementation) in the sense that Google as the data provider in this > story can state "here is the security system in place, that's what can > happen, here is the way to disallow the property to access the data > again" and individual problems, like the ones the calendar is having > right now. > > Those are bugs, and they will get fixed over time. For us, it is better > than not having a good story in the first place, as this is an issue for > all services that provide GData.
Ok. I had to push the issue a bit simply because I am receiving pressure from clients to 'just make it work'. I believe you are taking the right approach. Please accept my vote (and by proxy, a number of votes from folks who are pushing me) to fix the AuthSub hosted client support. Thanks again for taking the time to respond. Is Google working on providing their own sync solution? Cheers. -- Free replacement for Exchange and Outlook (Contacts and Calendar) http://www.ScheduleWorld.com/tg/ WebDAV: http://www.ScheduleWorld.com/sw/webDAVDir/4000.ics VFREEBUSY: http://www.ScheduleWorld.com/sw/freebusy/4000.ifb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi -~----------~----~----~----~------~----~------~--~---
