Chris, Thanks for the response. Jason had ping'd me the Partuza URL in IRC prior to me posting my question so I was able to see something like what I'd expect when I make a discovery request to a "vanilla" shindig. For us, Partuza is a great first step, but since we would like to build a container that is Java based, I'm not sure the php code from partuza will fit. That said, I realized, based on your note, that the URL I was hitting is wrong. Based on your feedback, here's what I tried:
Http Request: GET / HTTP/1.1 Accept: application/xrds+xml User-Agent: Jakarta Commons-HttpClient/3.1 Host: localhost:8080 And the response http header: HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Content-Length: 476 Server: Jetty(6.1.9) And the response body: <HTML><HEAD><TITLE>Directory: /</TITLE></HEAD><BODY> <H1>Directory: /</H1><TABLE BORDER=0><TR><TD><A HREF="/META-INF/">META-INF/ </TD><TD ALIGN=right>102 bytes </TD><TD>Nov 7, 2008 4:04:56 PM</TD></TR> <TR><TD><A HREF="/WEB-INF/">WEB-INF/ </TD><TD ALIGN=right>272 bytes </TD><TD>Nov 7, 2008 4:04:56 PM</TD></TR> <TR><TD><A HREF="/gadgets/">gadgets/ </TD><TD ALIGN=right>102 bytes </TD><TD>Nov 7, 2008 4:04:55 PM</TD></TR> </TABLE> </BODY></HTML> Clearly not the document we are looking to get back. Which brings me back to my original question. Does shindig provide hooks for this out of the box or is this something that I've got to implement on my own? I was also wondering if discovery is required by the containers. Section 5 of the REST spec says that the container MUST support the service types below and MAY support other ones. But it does not say if the container must support discovery. Thanks, -Mark W. _______________________________________________________________________________________________________________ Mark Weitzel | STSM | IBM Software Group | (919) 543 0625 | [EMAIL PROTECTED] From: Chris Chabot <[EMAIL PROTECTED]> To: [email protected] Date: 11/19/2008 05:07 AM Subject: Re: container discovery support Normally the URL you would hit for XRDS-simple discovery is the main site url, and not the shindig server instance, ie http://www.partuza.nl and not http://some.instance.thats.not.documented.partuza.nl :-) If you want to play with XRDS support, check http://www.partuza.nl, it supports pretty much all end-points you might want to test against (opensocial, oauth and portablecontacts): http://www.chabotc.com/xrds-test.php?url=http://www.partuza.nl ps, to use the 3 legged oauth support, register on partuza.nl, click 'edit' next to your name and go to the 'oauth' tab to get a oauth consumer key and secret to use (yes i'm aware these should be per-app and not per person, but for the quick and dirty testing this was easier :P) On Wed, Nov 19, 2008 at 4:17 AM, Mark D Weitzel <[EMAIL PROTECTED]> wrote: > I am trying to get the discovery information from a shindig container > running on localhost. > Here's the http header: > GET /social/rest/ HTTP/1.1 > Accept: application/xrds+xml > User-Agent: Jakarta Commons-HttpClient/3.1 > Host: localhost:8080 > > > And here's the http response header: > HTTP/1.1 501 The service is not implemented > Content-Type: text/html; charset=iso-8859-1 > Content-Length: 1442 > Server: Jetty(6.1.9) > > And the response body: > <html> > <head> > <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> > <title>Error 501 The service is not implemented</title> > </head> > <body><h2>HTTP ERROR: 501</h2><pre>The service is not implemented</pre> > <p>RequestURI=/social/rest/</p><p><i><small><a href=" > http://jetty.mortbay.org/";>Powered by Jetty://</a></small></i></p><br/> > > > So, this may be a silly question, but am I doing something wrong, or is > support for discovery not yet implemented in shindig? > > Thanks in advance for the help! > > -Mark W. > > _______________________________________________________________________________________________________________ > Mark Weitzel | STSM | IBM Software Group | (919) 543 0625 | > [EMAIL PROTECTED]
