You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Leonardo <st...@gmail.com> on 2008/06/19 23:53:21 UTC
A question about Data Integration
Hi all,
I'm new to this ML and to the Shindig world, I'm trying to understand
all the flow,
so please forgive me if I don't know all the concepts.. (and for my
english too ;) )
I'm playing with the php container.
I have a webapp I would like to "OpenSocialize", it is written in Ruby On Rails.
I understood that the bridge between the container and the DB is
located in the 3 classes
BasicPeopleService, BasicActivitiesService and BasicDataHandler.. right?
Now, instead of coding there all the SQL necessary to query my DB
I would like to know if there's a standard way to "communicate" with
my Rails Application (server-to-server) and what steps are required to
my Rails App in order to be OpenSocialized .. (e.g. becoming an OAuth
provider..)
Thank to all,
leonardo
Re: A question about Data Integration
Posted by Leonardo <st...@gmail.com>.
hi,
I found partuza some days ago... it looks very interesting.
I'm trying to understand how this could be done in Ruby On Rails.
thanks
leo
On Fri, Jun 20, 2008 at 1:24 AM, Chris Chabot <ch...@xs4all.nl> wrote:
> if you can read PHP ok, i would also sugest taking a look at partuza:
>
> http://code.google.com/p/partuza/
> live version: http://partuza.us.chabotc.com/
>
> it does authentication on the site part (partuza), then builds an secure
> iframe token which includes the owner/viewer info .. and thats the part of
> the 'secure authentication'
>
> the other way around ... well you could re-use the same token really, or
> anything else you want to code :)
>
> -- Chris
>
> On Jun 20, 2008, at 1:08 AM, Leonardo wrote:
>
>> I'm not shure I understood everything.
>> I'm talking about a scenario in which my Shindig and my webapp are in
>> separate layers.
>> If I don't implement some sort of authorization mechanism in my app
>> server (let's say the rails webapp which need to be opensocialized)
>> how can it trust the incoming request? how can my webapp says "ok, I
>> got a request from the Shindig container, here are the data you
>> requested"?
>> I'm a bit confused about this, however tomorrow I'll take a look at
>> the socialrest dir... maybe it will help :)
>>
>> thank you all for all the replies!
>> leo
>>
>>
>>
>> On Fri, Jun 20, 2008 at 12:21 AM, Chris Chabot <ch...@xs4all.nl> wrote:
>>>
>>> You don't have to OAuth your web app to become an open social container,
>>> Shindig takes care of all the gadget facing communication for you,
>>> including
>>> OAuth.
>>>
>>> There's no server to server protocol implemented yet, but there's no
>>> particular reason why you couldn't put some kind of RPC code in the data
>>> handler classes instead of SQL DB code ...
>>>
>>> Keep in mind we're switching wire format protocols (from some custom json
>>> based which you can find in /src/socialdata) to a new RESTful based one
>>> which is part of the v.8 specification, you can find this code in
>>> /src/socialrest ... it's probably better to base your work on the classes
>>> in
>>> there (see /src/socialrest/samplecontainer for the example files)
>>>
>>> -- Chris
>>>
>
>
Re: A question about Data Integration
Posted by Chris Chabot <ch...@xs4all.nl>.
if you can read PHP ok, i would also sugest taking a look at partuza:
http://code.google.com/p/partuza/
live version: http://partuza.us.chabotc.com/
it does authentication on the site part (partuza), then builds an
secure iframe token which includes the owner/viewer info .. and thats
the part of the 'secure authentication'
the other way around ... well you could re-use the same token really,
or anything else you want to code :)
-- Chris
On Jun 20, 2008, at 1:08 AM, Leonardo wrote:
> I'm not shure I understood everything.
> I'm talking about a scenario in which my Shindig and my webapp are in
> separate layers.
> If I don't implement some sort of authorization mechanism in my app
> server (let's say the rails webapp which need to be opensocialized)
> how can it trust the incoming request? how can my webapp says "ok, I
> got a request from the Shindig container, here are the data you
> requested"?
> I'm a bit confused about this, however tomorrow I'll take a look at
> the socialrest dir... maybe it will help :)
>
> thank you all for all the replies!
> leo
>
>
>
> On Fri, Jun 20, 2008 at 12:21 AM, Chris Chabot <ch...@xs4all.nl>
> wrote:
>> You don't have to OAuth your web app to become an open social
>> container,
>> Shindig takes care of all the gadget facing communication for you,
>> including
>> OAuth.
>>
>> There's no server to server protocol implemented yet, but there's no
>> particular reason why you couldn't put some kind of RPC code in the
>> data
>> handler classes instead of SQL DB code ...
>>
>> Keep in mind we're switching wire format protocols (from some
>> custom json
>> based which you can find in /src/socialdata) to a new RESTful based
>> one
>> which is part of the v.8 specification, you can find this code in
>> /src/socialrest ... it's probably better to base your work on the
>> classes in
>> there (see /src/socialrest/samplecontainer for the example files)
>>
>> -- Chris
>>
Re: A question about Data Integration
Posted by Leonardo <st...@gmail.com>.
I'm not shure I understood everything.
I'm talking about a scenario in which my Shindig and my webapp are in
separate layers.
If I don't implement some sort of authorization mechanism in my app
server (let's say the rails webapp which need to be opensocialized)
how can it trust the incoming request? how can my webapp says "ok, I
got a request from the Shindig container, here are the data you
requested"?
I'm a bit confused about this, however tomorrow I'll take a look at
the socialrest dir... maybe it will help :)
thank you all for all the replies!
leo
On Fri, Jun 20, 2008 at 12:21 AM, Chris Chabot <ch...@xs4all.nl> wrote:
> You don't have to OAuth your web app to become an open social container,
> Shindig takes care of all the gadget facing communication for you, including
> OAuth.
>
> There's no server to server protocol implemented yet, but there's no
> particular reason why you couldn't put some kind of RPC code in the data
> handler classes instead of SQL DB code ...
>
> Keep in mind we're switching wire format protocols (from some custom json
> based which you can find in /src/socialdata) to a new RESTful based one
> which is part of the v.8 specification, you can find this code in
> /src/socialrest ... it's probably better to base your work on the classes in
> there (see /src/socialrest/samplecontainer for the example files)
>
> -- Chris
>
RE: A question about Data Integration
Posted by "Ruffin, John" <jr...@achfood.com>.
Chris, I had a similar question to this yesterday (Data Integration:
Guidance). I created a DAO layer which provides access to a db schema
based on the open_social.sql script on your website.
So, should I make calls from /src/socialrest to this layer somehow?
BTW, enjoyed chatting @ Google I/O.
-----Original Message-----
From: Chris Chabot [mailto:chabotc@xs4all.nl]
Sent: Thursday, June 19, 2008 5:21 PM
To: shindig-dev@incubator.apache.org
Subject: Re: A question about Data Integration
You don't have to OAuth your web app to become an open social
container, Shindig takes care of all the gadget facing communication
for you, including OAuth.
There's no server to server protocol implemented yet, but there's no
particular reason why you couldn't put some kind of RPC code in the
data handler classes instead of SQL DB code ...
Keep in mind we're switching wire format protocols (from some custom
json based which you can find in /src/socialdata) to a new RESTful
based one which is part of the v.8 specification, you can find this
code in /src/socialrest ... it's probably better to base your work on
the classes in there (see /src/socialrest/samplecontainer for the
example files)
-- Chris
On Jun 19, 2008, at 11:53 PM, Leonardo wrote:
> Hi all,
> I'm new to this ML and to the Shindig world, I'm trying to understand
> all the flow,
> so please forgive me if I don't know all the concepts.. (and for my
> english too ;) )
> I'm playing with the php container.
> I have a webapp I would like to "OpenSocialize", it is written in
> Ruby On Rails.
> I understood that the bridge between the container and the DB is
> located in the 3 classes
> BasicPeopleService, BasicActivitiesService and BasicDataHandler..
> right?
> Now, instead of coding there all the SQL necessary to query my DB
> I would like to know if there's a standard way to "communicate" with
> my Rails Application (server-to-server) and what steps are required to
> my Rails App in order to be OpenSocialized .. (e.g. becoming an OAuth
> provider..)
>
>
> Thank to all,
> leonardo
This email and its attachments are confidential, subject to copyright and may be legally privileged. If they have come to you in error you should take no action based upon the contents nor should you copy or show them to anyone. Please delete the email and its attachments and inform admin@achfood.com. Any views or opinions expressed are those of the author and do not necessarily represent those of ACH Food Companies, Inc.
Security: Internet email is not a completely secure medium, please note this when considering the content of your message.
Viruses: We take precautions to ensure email is free of viruses but cannot make a guarantee. Accordingly we advise scanning all email and attachments.
Re: A question about Data Integration
Posted by Chris Chabot <ch...@xs4all.nl>.
You don't have to OAuth your web app to become an open social
container, Shindig takes care of all the gadget facing communication
for you, including OAuth.
There's no server to server protocol implemented yet, but there's no
particular reason why you couldn't put some kind of RPC code in the
data handler classes instead of SQL DB code ...
Keep in mind we're switching wire format protocols (from some custom
json based which you can find in /src/socialdata) to a new RESTful
based one which is part of the v.8 specification, you can find this
code in /src/socialrest ... it's probably better to base your work on
the classes in there (see /src/socialrest/samplecontainer for the
example files)
-- Chris
On Jun 19, 2008, at 11:53 PM, Leonardo wrote:
> Hi all,
> I'm new to this ML and to the Shindig world, I'm trying to understand
> all the flow,
> so please forgive me if I don't know all the concepts.. (and for my
> english too ;) )
> I'm playing with the php container.
> I have a webapp I would like to "OpenSocialize", it is written in
> Ruby On Rails.
> I understood that the bridge between the container and the DB is
> located in the 3 classes
> BasicPeopleService, BasicActivitiesService and BasicDataHandler..
> right?
> Now, instead of coding there all the SQL necessary to query my DB
> I would like to know if there's a standard way to "communicate" with
> my Rails Application (server-to-server) and what steps are required to
> my Rails App in order to be OpenSocialized .. (e.g. becoming an OAuth
> provider..)
>
>
> Thank to all,
> leonardo