Oh and another generic suggestion:
If you use something like mod_proxy in apache, you could easily use php or
java shindig for the /social (REST, RPC API) or /gadgets (Gadget rendering,
meta data interface, etc) part of the implementation, and use that to
implement the other end.. this way you'll be able to test the functioning of
it a lot quicker as when you try to do both at once.
Also it's quite ok to depend on the javascript implementation of os-data and
os-templates for the first version, so you can knock that of your todo list
in the beginning.
And final suggestion, make sure to ping the shindig-dev list whenever
something is unclear :)
-- Chris
On Mon, May 11, 2009 at 4:57 PM, Chris Chabot <[email protected]> wrote:
> Here's one such reference to get you started:
>
>
> http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/de729f6f34c45e12/c7b9328a11ab6f1a?hl=en&#c7b9328a11ab6f1a
>
>
>
>
> On Mon, May 11, 2009 at 4:54 PM, Fisher, Tim <[email protected]>wrote:
>
>> Chris,
>>
>> Good idea, thanks for the suggestion. I will do that.
>>
>> Tim
>>
>> -----Original Message-----
>> From: Chris Chabot [mailto:[email protected]]
>> Sent: Monday, May 11, 2009 10:50 AM
>> To: [email protected]
>> Subject: Re: Ruby Port of Shindig
>>
>> I also remember a few cases where people said they had the intention
>> too; Might be worth digging up those posts and contacting them directly
>> too? Some might not be subscribed to the shindig-dev list.
>>
>> & good luck!
>>
>> -- Chris
>>
>> On Mon, May 11, 2009 at 4:43 PM, Fisher, Tim
>> <[email protected]>wrote:
>>
>> > Would anyone out there be interested in contributing to a Ruby port of
>>
>> > Shindig?? Scanning the mailing list and searching the web I notice
>> > that have been a few false starts at a Ruby implementation of Shindig.
>>
>> > I'd like to get a small team together of developers interested in
>> > completing this project, a full Shindig implementation in Ruby.
>> >
>> > If your interested drop me a line... [email protected]
>> >
>> > Thanks,
>> > Tim
>> > The contents of this e-mail are intended for the named addressee only.
>>
>> > It contains information that may be confidential. Unless you are the
>> > named addressee or an authorized designee, you may not copy or use it,
>>
>> > or disclose it to anyone else. If you received it in error please
>> > notify us immediately and then destroy it.
>> >
>>
>
>
