Thanks Chris.

Yes I'll be open sourcing it.  I'm working on the rpc/rest api's and
the http proxy first, since those are the parts that you really need
if you want to integrate with an existing ruby app.  Right now I have
the container setup so you can run the php or java version on the side
and use it to provide the gadget rendering and metadata services.  I
basically take the rendered gadget from shindig, replace a few url's,
and then store that in the container database.   So far that seems to
work fairly well.  I'm hoping to have a working container with rest/
rpc/makerequest support within the month.

One approach I initially looked at was providing some type of plugin
for the java version using jruby, which would let you just implement
the existing stubs using ruby.  But to get very much traction in the
ruby world,  I think it needs to all be ruby.   I don't see very many
ruby/rails houses wanting to hire someone to manage java deployments
alongside their rails deployments.

I've been working off the php codebase, and the Partuza stuff was a
big help in figuring out how to write a container and integrate that
with shindig.

Chris

On Dec 30, 4:37 am, Chris Chabot <[email protected]> wrote:
> Heya Chris,
>
> Currently the trunk and 1.0 branch are identical, but that will change quite
> soon as 0.9 implementation work starts; Since for porting a more stable code
> base is very useful the 1.0 branch is probably a better target.
>
> Ps, will you be opensourcing this? And any idea when this will be publicly
> available?
>
>    -- Chris
>
> On Wed, Dec 24, 2008 at 12:29 PM, snacktime <[email protected]> wrote:
>
> > I've started an implementation of shindig in ruby and  have been using
> > the php version from trunk as a reference.  Should I be using the
> > 1.0.x from branches instead?
>
> > Chris
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to