Why don't you own the calendar and share it, read only, with the user? Ray
On Wed, Jul 13, 2011 at 5:29 AM, NatoCM <[email protected]> wrote: > Hi, > > I'd like to create a calendar for a user with events from our app that is > read-only in Google Calendar. We'll be regularly updating the calendar as > data changes in our app. If the user is able to modify the calendar in > Google Calendar, it could result in a bad user experience, as they might > expect that their changes would be reflected in our app (2-way synch). Plus > we might end up wiping out any events they added themselves. > > I've tried various approaches of setting the AccessLevel property on the > calendar (ignored, I could still edit the calendar) and trying to change the > user's ACL entry (500 error response when I tried to change the owner to > read), with no luck. The other approach we could take would be to publish > our data in iCal format, but it looks like that doesn't allow us to refresh > the data reliably. > > This seemed like a pretty common, straightforward use case. Anybody know > how it might be accomplished? > > (this question was originally posted by "brianharper" on the older forum, > but I could'n find any answer to it, so I'm resubmitting it to you guys. > Thanks...) > > -- > 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://code.google.com/apis/calendar/community/forum.html > -- 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://code.google.com/apis/calendar/community/forum.html
