In the GData APIs the gd:etag attribute only seems to be set if the client specifies the 2.1 version of the protocol. This is fine, since the Java library seems to default to using it, and correctly parses out the ETag so it can be used on the client application side.
However, we're working with a third party that is using the .NET library. That library seems to default to the 2.0 protocol, which doesn't include the ETag. We can force the library to use 2.1 by appending ?v=2.1 to the end of the request URIs, but the library never seems to actually pick up the -- now present -- ETag attribute. Specifically, this is for the Calendar and Contacts API, though from preliminary testing it seems to be a "feature" of the .NET GData library. Any ideas on how to convince the .NET library to read the ETag? 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
