You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by victor <vi...@gmail.com> on 2008/01/27 14:13:11 UTC
Sample container features and roadmap ?
Hi,
Following Google suggestion
(http://opensocialapis.blogspot.com/2008/01/six-apart-hackathon-wrap-up-and-caja.html),
I would like to know :
- when the sample container will support makeRequest ? (and if the
signed request feature will be available)
- how can we be updated with new features and roadmap on the sample
container ?
Thank you
Victor
Re: Sample container features and roadmap ?
Posted by victor <vi...@gmail.com>.
Thanks very much for this very helpful answer, so I will continu to
watch this mailing list :)
Victor
> Hi Victor,
>
> On Jan 27, 2008 5:13 AM, victor <vi...@gmail.com> wrote:
>
>
>> Hi,
>>
>> Following Google suggestion
>> (
>> http://opensocialapis.blogspot.com/2008/01/six-apart-hackathon-wrap-up-and-caja.html
>> ),
>> I would like to know :
>> - when the sample container will support makeRequest ? (and if the
>> signed request feature will be available)
>>
>
>
> makeRequest is now a part of gadgets core (specifically, gadgets.io), and is
> no longer strictly an open social feature as of 0.7 (
> http://code.google.com/apis/gadgets/docs/reference/gadgets.io.html,
> http://code.google.com/apis/opensocial/docs/0.7/reference/opensocial.html).
> Shindig is implementing against this specification. gadgets.io has partial
> support for signing and only placeholders for full oauth. Both of these
> features are high on the radar, but as to who implements and when it rolls
> out is hard to say. Patches are more than welcome. Currently shindig doesn't
> implement any opensocial version correctly at all (you'll notice that
> there's no opensocial-0.x in the features/ directory).
>
>
>
>> - how can we be updated with new features and roadmap on the sample
>> container ?
>>
>
>
> The sample container is a tiny area of development for the project that
> exists for reference and testing purposes; most of our efforts at this point
> in time are focused on the following items:
>
> - Achieve full compliance with the core gadgets javascript API spec (main
> issues: gadgets.rpc, gadgets.io.makeRequest, gadgets.views)
> We're pretty close here. gadgets.rpc will default to using IFPC, and
> makeRequest just needs to support the signing token throughout the stack.
> OAuth is trickier, but less critical than other pieces right now.
> gadgets.views is a relatively simple JS library, but it also requires server
> side work.
>
> - Create a compliant implementation of opensocial 0.7.
> This will most likely consist of figuring out a way to refactor the
> opensocial-reference and opensocial-samplecontainer features in such a way
> that better hooks are provided for sites that want to integrate using
> shindig, and then moving everything into the opensocial-0.7 feature. The
> current setup requires dropping in a custom implementation for every site,
> and that's annoying to work with. We have no plans on implementing older
> opensocial API versions at this point in time.
>
> - Improve server code to make configuration easier. Right now there is no
> clean way for integrators to plug in their own caching, fetching, and
> signing infrastructure other than to write custom servlet filters and hack
> up some of the servlet code. This needs to be addressed soon with a DI
> framework.
>
> The closest thing that we have to a roadmap right now are the open JIRA
> issues. We probably won't have a real roadmap until we get to the point of
> stable releases, and the sample container will likely never have a roadmap
> of its own. The best way to find out when things have changed is to watch
> this mailing list and look for commits and changes to JIRA.
>
> ~Kevin
>
>
Re: Sample container features and roadmap ?
Posted by Kevin Brown <et...@google.com>.
Hi Victor,
On Jan 27, 2008 5:13 AM, victor <vi...@gmail.com> wrote:
> Hi,
>
> Following Google suggestion
> (
> http://opensocialapis.blogspot.com/2008/01/six-apart-hackathon-wrap-up-and-caja.html
> ),
> I would like to know :
> - when the sample container will support makeRequest ? (and if the
> signed request feature will be available)
makeRequest is now a part of gadgets core (specifically, gadgets.io), and is
no longer strictly an open social feature as of 0.7 (
http://code.google.com/apis/gadgets/docs/reference/gadgets.io.html,
http://code.google.com/apis/opensocial/docs/0.7/reference/opensocial.html).
Shindig is implementing against this specification. gadgets.io has partial
support for signing and only placeholders for full oauth. Both of these
features are high on the radar, but as to who implements and when it rolls
out is hard to say. Patches are more than welcome. Currently shindig doesn't
implement any opensocial version correctly at all (you'll notice that
there's no opensocial-0.x in the features/ directory).
>
> - how can we be updated with new features and roadmap on the sample
> container ?
The sample container is a tiny area of development for the project that
exists for reference and testing purposes; most of our efforts at this point
in time are focused on the following items:
- Achieve full compliance with the core gadgets javascript API spec (main
issues: gadgets.rpc, gadgets.io.makeRequest, gadgets.views)
We're pretty close here. gadgets.rpc will default to using IFPC, and
makeRequest just needs to support the signing token throughout the stack.
OAuth is trickier, but less critical than other pieces right now.
gadgets.views is a relatively simple JS library, but it also requires server
side work.
- Create a compliant implementation of opensocial 0.7.
This will most likely consist of figuring out a way to refactor the
opensocial-reference and opensocial-samplecontainer features in such a way
that better hooks are provided for sites that want to integrate using
shindig, and then moving everything into the opensocial-0.7 feature. The
current setup requires dropping in a custom implementation for every site,
and that's annoying to work with. We have no plans on implementing older
opensocial API versions at this point in time.
- Improve server code to make configuration easier. Right now there is no
clean way for integrators to plug in their own caching, fetching, and
signing infrastructure other than to write custom servlet filters and hack
up some of the servlet code. This needs to be addressed soon with a DI
framework.
The closest thing that we have to a roadmap right now are the open JIRA
issues. We probably won't have a real roadmap until we get to the point of
stable releases, and the sample container will likely never have a roadmap
of its own. The best way to find out when things have changed is to watch
this mailing list and look for commits and changes to JIRA.
~Kevin