The webbased ICAL import is actually keeping the UID from the ICS file
- it's only doing a special BASE32 converting ...  if there is a ID
collision, it will overwrite older 'imported' events - but never events
created in GCAL (a Bug..)

So, if it would be possibly to upload an ICS file directly with
API/authentication...it would be a workaround.

I vote for Client Event ID Generation ;-)

Cheers,
Roland 
(iCal4OL)


--~--~---------~--~----~------------~-------~--~----~
 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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to