This is an accurate statement of how the current implementation works, but I
think it is less than ideal. The same piece of content (projected in
different ways) is still a single piece of data and should have a constant
ID across all projections. I've actually opened up a bug against the
Calendar service to resolve this, but the tricky aspect is that fixing it
means the ID will change for some set of projections (i.e. to unify to a
single ID for all of them).
In the interim, Ryan's suggestion is a great one and should be robust both
before and after a fix is made. Just compare the last path element, which
is itself a GUID and is constant across all projections. When this is
fixed, this property of the resulting IDs will remain true, but there will
be the added ability to just do an absolute ID comparison and get the right
result as well.
Cheers!
-- Kyle
On 11/28/06, Ryan Boyd (Google) <[EMAIL PROTECTED]> wrote:
>
>
> Hi Mikael,
>
> The full IDs aren't exactly the same, as the feed which the events came
> from and the entry content is different (depending upon the projection
> and visibility), but you can derive one from the other.
>
> The component of the ID after the last slash ('/') should be the same
> across each of the projections and visibilities.
>
> For instance:
>
> The following is the content of the id element in a basic feed:
>
> http://www.google.com/calendar/feeds/default/private/basic/fjs4j7258bsoi19hvpvdp68qg8
>
> Should have the same ending in the full feed:
>
> http://www.google.com/calendar/feeds/default/private/full/fjs4j7258bsoi19hvpvdp68qg8
>
> Hope this answers your question.
>
> Happy Coding,
>
> -Ryan
>
>
> On Nov 16, 12:12 pm, "Mikael Grev, MiG InfoCom" <[EMAIL PROTECTED]>
> wrote:
> > Thanks Kyle,
> >
> > I'm wondering about this thing with theID. I just got the feeling that
> > the same entry get different IDs depending on the feed used to get it??
> > Please say it isn't so! That would mean that it really isn't anID,
> > it's anIDwith a path to a system that can have symbolic links...
> >
> > Cheers,
> > Mikael
> >
> > On Nov 15, 11:48 pm, "Kyle Marvin" <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > Hi Mikael,
> >
> > > This sounds like a bug. TheIDvalues should be absolute URIs, not
> relative
> > > ones. I'm going to open a bug on this. In the interim, I think the
> > > following test should be OK to test for equivalence in the interim:
> >
> > > event.getID().endsWith(originalID);
> >
> > > since just testing the relative (last) path component is enough to
> guarantee
> > > equivalence.
> >
> > > When we resolve this bug and provide absolute IDs instead, the above
> test
> > > will continue to work.
> >
> > > Hope this helps!
> >
> > > -- Kyle
> >
> > > On 11/15/06, Mikael Grev, MiG InfoCom <[EMAIL PROTECTED]> wrote:
> >
> > > > Hello,
> >
> > > > TheIDgotten withevent.getID() is including the URL. Now, theID
> > > > gotten from OriginalEvent is without the url part and only contains
> the
> > > > end (true)id.
> >
> > > > Is there a standard way to get theIDwithout the url from the normal
> > > >eventso they can be compared or should we do the conversion
> ourselves?
> > > > It would if so be good to know how in a way that will hold for
> future
> > > > updates.
> >
> > > > Cheers,
> > > > Mikael Grev- Hide quoted text -- Show quoted text -
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
