I don't see why a new event should have the same ID as a deleted one, that's really messy.
you are right, it would indeed be messy to add a new event with an old id, ...but in fact i want to be able to add the 'same' event again... - the event i hand over to the service has no "id" set, the managament of the "id"-attributes is done by google calendar. ...the event is only filled with data from the ical source of course including an "icalUID". to conclude: i think the management of icalUIDs should be left to the external (ical) source... :0) btw.: now i have a (dirty) workaround: when reading data from the ical i append "System.currentTimeMillis()" to the icalUIDs, ...so i still have the connection to the original data after removing the timestamp. - its definately not the best way, but for now it works.... -- 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
