With the upcoming 2.0 implementation in Shindig 3, some of us may face
the need to have multiple API versions up and running (e.g. OpenSocial
1.0 and OpenSocial 2.0) as we want to make the move from Shindig 2 to 3
easy for our users. Currently -if I am correct - OpenSocial has nothing
on version the REST API, but the gadgets are able to explicitly request
a OS version. Is this by choice? Should the REST API also include some
sort of version? Do we as the spec community consider this an
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
+1 for versioning the api through HTTP headers, but instead of
creating our own custom header, we should just use the "Accept"
header, which was meant to be used for versioning :)
On Sun, Feb 5, 2012 at 12:55 AM, Niels van Dijk