Actually XRDS is a container affair that has little to do with
shindig, since you have to send the XRDS discovery request to the main
site URL (www.example.org), and not to it's open social server (which
could be any host name like 'foo123.v2.hosted.api.example.org').
See http://xrds-simple.net/core/1.0/#go_fetch
I did build XRDS support into Partuza to be able to play with it, see:
http://www.chabotc.com/opensocial/xrds-fetcher-tool-and-shindig-atom-support/
About where the HEAD or GET request needs to go too, the XRDS document
tells you the location of the people, appdata and activity URL's and
in which way you can define the resources you want to address.
Hope that helps!
-- Chris
On Aug 8, 2008, at 9:52 PM, Rajdeep Dua wrote:
Hi,
I couldnt find the XRDS implementation in the shindig code, Is it
already
being implemented or in the process.
Another point which is not very clear is at what endpoint should the
HTTP
HEAD or HTTP GET request should go
(Say my shindig server is running at http://localhost:8080)
Thanks
Rajdeep
