Hi Jerome,
I've ran into the same problems with the 0.8 compliance test gadget, and did
send an email to the author about it, seems to be a javascript error in the
code, I'm sure it'll get fixed eventually!
As mentioned before, nothing is going to be removed, php-shindig will
support both the REST API (in the required json + atom dialects, plus in the
optional xml dialect), and also the JSON-RPC API. So it'll do everything you
could possible want out of it :)
On Fri, Oct 17, 2008 at 4:11 PM, nvgigigan <[EMAIL PROTECTED]> wrote:
>
> Hi Chris,
>
> Two simple question:
> - Is there a 0.8 compliance test? I found some kind of 0.8 compliance
> (opensocial-resources) test gadget but no one loads (I hope it's not
> because I'm so NOT compliant :D)
> - I understood for the REST API specification in opensocial, but I
> wanted to know if you're going to remove the PHP/REST ("client side")
> part of shindig?
>
> Again you do a real good job and I'm sure it will be soon a easy-
> pleasure to install shindig
>
> Have a nice day
>
> Jerome
>
> On Oct 16, 1:33 pm, "Chris Chabot" <[EMAIL PROTECTED]> wrote:
> > Those numbers i'm getting with the standard 0.7 container compliance test
> > gadget:
> http://opensocial-resources.googlecode.com/svn/tests/trunk/suites/0.7...
> >
> > if you head over towww.partuza.nl(publicly hosted demo that's running
> the
> > latest code), you can create a profile there and add that gadget to your
> > profile if you want to have a good reference.
> >
> > Hope it helps!
> >
> > -- Chris
> >
> > On Thu, Oct 16, 2008 at 1:29 PM, nvgigigan <[EMAIL PROTECTED]> wrote:
> >
> > > Thanks for the quick reply,
> > > I guess I have something wrong in my installation (which is not a
> > > basic case I bet that's why)
> > > but tell me how you drive your test? Are you using the specific
> > > gadget? Which version?
> > > Btw you do a great job with all the partuza thing :)
> >
> > > Have a nice day
> >
> > > Jerome
> >
> > > On 16 oct, 13:19, "Chris Chabot" <[EMAIL PROTECTED]> wrote:
> > > > Hi Jerome,
> >
> > > > No REST is not going away, I think the comment that you read is about
> the
> > > > gadget <-> shindig communication to support the JS API, which used to
> > > work
> > > > over the REST protocol and has now switched over to using the
> json-rpc
> > > > protocol (so we switched from
> > > > shindig/features/opensocial-rest/restfulcontainer.js to
> > > > shindig/features/opensocial-jsonrpc/jsonrpccontainer.js to drive the
> JS
> > > > API).
> >
> > > > If you read the specification you'll see that the REST protocol is a
> > > *MUST*
> > > > (RFC talk), and JSON-RPC is optional, however we decide to support it
> > > since
> > > > it provides a great way of batching requests, and guaranteeing
> request
> > > > ordening, so it's a great protocol to use and support, so both will
> keep
> > > > having a place in shindig.
> >
> > > > If you would update to the most recent php-shindig and partuza code
> > > (maybe
> > > > start out fresh to make sure there's no conflicts and/or old code
> laying
> > > > around) you should be getting 120 tests passed in the container
> > > compliance
> > > > test, and 8 tests failed. (5 of which are known to broken in the test
> > > it's
> > > > self, so 3 more left to fix really :).
> >
> > > > If your getting different results in your complaince test, then
> there's
> > > > something wrong in your instalation and it might be good to double
> check
> > > if
> > > > your configuration is fully working.
> >
> > > > So please, continue to use REST and no need to worry about that, and
> if
> > > you
> > > > update to the latest code you'll find the test results are a lot
> better
> > > now
> > > > then the numbers you mentioned :)
> >
> > > > -- Chris
> >
> > > > On Thu, Oct 16, 2008 at 11:34 AM, nvgigigan <[EMAIL PROTECTED]>
> wrote:
> >
> > > > > I read somewhere in the shindig code that you will remove the REST
> > > > > support?
> > > > > Is that true? Or will you keep REST compatibility?
> > > > > For now I tested partuza with RPC and I get 92 tests passed, only
> 75
> > > > > with REST...
> > > > > Do you know something about Opensocial specification? Are they
> going
> > > > > to keep both (I saw that RPC is a may implement for container but
> it
> > > > > can change to a MUST and vice-versa for REST)
> >
> > > > > Should I continue to implement the REST API in my container?
> > > > > Anyway I think we're going to use shindig for all the opensocial
> > > > > part :)
> >
> > > > > Have a nice day
> >
> > > > > Jerome
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Implementing OpenSocial Containers" 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/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---
