Hi all,
I wanted to clarify some points over this.
If I m developing a social site based on the open social API, i need to have
both the container as well as the gadget server. Now I m a bit confused about
the functions of these two.
1.. first of all, who generates the security token containing the information
about the owner, viewer and token id.
2.. This token is then passed to the gadget server along with the application
url.
3.. Now what will the gadget server do with this token?
4.. If any site data is required, then the gadget server will call the
container for the data, the container will return the data as json string to
the gadget server. Is this correct?
5.. Now, out of this, what has been integrated in shindig?
Can someone please reply to these points as based on this I need to start my
work.
Regards
Lini Haridas
Software Engineer
[EMAIL PROTECTED]
Clarion Technologies
SEI CMMI Level 3 Company
4th Floor, Great Eastern Plaza,
Airport Road,
Pune- 411 006,
Maharashtra, India.
Phone: +91 20 66020289
Mobile: +91 9823435917
www.clariontechnologies.co.in
----- Original Message -----
From: "John Hjelmstad" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 02, 2008 12:13 AM
Subject: Re: Questions about implementing shindig
> Hi Jason:
>
> First off, it sounds like you're on the right track to me. A few notes:
>
> 1. If you're hosting gadgets on gadgets.site.com, you should make absolutely
> sure that any "important" (however you define this) cookies are stored only
> on www.site.com, *not* on .site.com. Ideally no cookies should be sent to
> any given gadget render.
>
> 2. Shindig doesn't yet have an OpenSocial JS implementation that uses the
> RESTful APIs. You're welcome to implement and contribute one though :)
>
> 3. I'm not 100% clear on what you mean by where you're supposed to set
> VIEWER and OWNER. These are passed in as hash-params to the gadget IFRAME,
> for instance. Is that what you mean?
>
> John
>
> On Wed, Apr 30, 2008 at 1:21 PM, Jason Burgess <[EMAIL PROTECTED]> wrote:
>
>> Now that I've got a working gadget server and some basic functionality. I
>> seem to be getting lost in the documentation for connecting my site's data
>> to it.
>>
>>
>>
>> Here's what I *think* is going to work based on what I've read. Please
>> correct me where I'm wrong. And there are still a few pieces of the puzzle
>> I'm missing, but I'll point them out along the way.
>>
>>
>>
>> I've got a main website, www.site.com, and a gadgets server,
>> gadgets.site.com.
>>
>>
>>
>> On gadgets.site.com, /gadgets is transparently proxied to the jetty
>> server,
>> while /social is transparently proxied back to www.site.com/social, so
>> that
>> gadgets.site.com believes it is coming from the same server.
>>
>>
>>
>> On /social/data, I'm implementing the RESTful API to retrieve data from the
>> main website's database.
>>
>>
>>
>> From what I understood, shindig will mediate between the RESTful API and
>> the
>> gadgets, but most of that isn't finished yet.
>>
>>
>>
>> From www.site.com, I'm implementing the container to call gadgets.site.com
>> to render the gadgets.
>>
>>
>>
>> One thing I'm still having trouble discerning is where in the container I'm
>> supposed to be setting VIEWER and OWNER.
>>
>>
>>
>> Hopefully, I'm at least headed in the right direction here.
>>
>>
>>
>> Jason
>>
>>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
