You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@abdera.apache.org by David Primmer <da...@gmail.com> on 2008/02/26 00:12:39 UTC
Shindig RESTful API server implementation
A group of us at Google have decided to try to implement the RESTful
Data API portion of the Shindig reference implementation with the Atom
framework Abdera. I believe this has been called the 'gateway server'.
We will implement whatever is decided on at
http://groups.google.com/group/opensocial-and-gadgets-spec.
We are hoping there will be an initial draft spec posted there soon.
Still, we can start now, before the wire formats are finalized, by
getting the basic servlets going and establish a place for people to
try out features. I wanted to send this initial message to the list to
let everyone know our intentions and start a discussion of what we
plan on doing. We have a few months experience using Abdera and with
the 0.4 release coming soon, now is a perfect time to kick off this
effort.
davep
reference links:
http://incubator.apache.org/abdera/
http://code.google.com/apis/opensocial/docs/dataapis.html
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
Sorry. I didn't realize that was the impression. My 'group' is the 3
engineers on the Google FeedServer project. When I approached some of
the Shindig members, they immediately suggested I post my intentions
to the list.
On to more technical matters:
One of the new additions to the Abdera project that is in 0.4 is the
concept of data adpaters. These adapters are essentially ways to
create feeds for existing data sources, like a database, filesystem or
ldap server. We've designed a few of them so that you only need to
edit a configuration file and you have read-write Atom Publishing --
no need to alter the code. Abdera is also a framework that allows you
to build your own adapters. Abdera adapters fit the gateway concept
well. I think adapters that produce the 3 main data apis in OpenSocial
should be created and maybe backed by something simple like the
filesystem or an embedded db.
davep
On Tue, Feb 26, 2008 at 7:39 AM, Brian W. Fitzpatrick <fi...@google.com> wrote:
> On Tue, Feb 26, 2008 at 9:05 AM, Brian McCallister <br...@skife.org> wrote:
> > I think it is a great thing to do, I just want to caution against "A group
> > of us at Google have decided..." as the perception that someone has to be a)
> > at google, and b) in the right conversation to make these decisions will
> > push away external contributors. Is frustrating at times, but when, in
> > situations like shindig, a project is being dominated by folks at one
> > company it matters.
> >
> > The best rule of thumb I know is to never make decisions offline or via a
> > backchannel. The phrase "a group of us at $VENDOR decided" just sets off
> > alarm bells in apache-land.
>
> I'd like to clarify a few things:
>
> David and his "group" are not affiliated in any way with Google's
> engineers contributing to Shindig. They're a completely separate
> group of developers who hadn't spoken with myself or any of the other
> folks contributing to Shindig before posting to the list.
>
> Leading in with "A group of us at Google have decided" was a
> mistake--it *did* give a totally wrong impression. Saying "Some
> friends and I have decided to implement FOO using Abdera." would have
> been much more appropriate.
>
> So I don't think there's a problem here--just a misunderstanding. The
> folks at Google who are contributing to Shindig understand the
> importance of discussing and deciding Shindig related matters on
> shindig-dev.
>
> -Fitz
>
Re: Shindig RESTful API server implementation
Posted by "Brian W. Fitzpatrick" <fi...@google.com>.
On Tue, Feb 26, 2008 at 9:05 AM, Brian McCallister <br...@skife.org> wrote:
> I think it is a great thing to do, I just want to caution against "A group
> of us at Google have decided..." as the perception that someone has to be a)
> at google, and b) in the right conversation to make these decisions will
> push away external contributors. Is frustrating at times, but when, in
> situations like shindig, a project is being dominated by folks at one
> company it matters.
>
> The best rule of thumb I know is to never make decisions offline or via a
> backchannel. The phrase "a group of us at $VENDOR decided" just sets off
> alarm bells in apache-land.
I'd like to clarify a few things:
David and his "group" are not affiliated in any way with Google's
engineers contributing to Shindig. They're a completely separate
group of developers who hadn't spoken with myself or any of the other
folks contributing to Shindig before posting to the list.
Leading in with "A group of us at Google have decided" was a
mistake--it *did* give a totally wrong impression. Saying "Some
friends and I have decided to implement FOO using Abdera." would have
been much more appropriate.
So I don't think there's a problem here--just a misunderstanding. The
folks at Google who are contributing to Shindig understand the
importance of discussing and deciding Shindig related matters on
shindig-dev.
-Fitz
Re: Shindig RESTful API server implementation
Posted by Brian McCallister <br...@skife.org>.
David,
I think it is a great thing to do, I just want to caution against "A group
of us at Google have decided..." as the perception that someone has to be a)
at google, and b) in the right conversation to make these decisions will
push away external contributors. Is frustrating at times, but when, in
situations like shindig, a project is being dominated by folks at one
company it matters.
The best rule of thumb I know is to never make decisions offline or via a
backchannel. The phrase "a group of us at $VENDOR decided" just sets off
alarm bells in apache-land.
-Brian
On Mon, Feb 25, 2008 at 9:32 PM, David Primmer <da...@gmail.com>
wrote:
> Hey Brian,
>
> I didn't mean to imply that Google as a company had decided the fate
> of the Shindig project in this area. Far from it, my team in Google is
> interested in using parts of Shindig and we needed an API server (a
> current gap), so thought we'd contribute some code to Shindig.
>
> One reason why it may appear that there was some hidden discussion is
> that there also happened to be an open source Java Atom server project
> that has been going on at Google since last spring. It uses Abdera
> http://code.google.com/p/google-feedserver/. We have been contributing
> code to Abdera for the last couple of months and have become familiar
> with the codebase. This effort was not coordinated or discussed with
> the Shindig list because it was started before OpenSocial / Shindig
> was conceived. So we have a situation where some experience was
> developed independent of OpenSocial that happened to be applicable.
>
> I hope this helps clarify it. I'm completely willing to discuss pros
> and cons of using Abdera. I think it's a very good server and I wanted
> to suggest that Shindig use it.
>
> davep
>
> On Mon, Feb 25, 2008 at 7:59 PM, Brian McCallister <br...@skife.org>
> wrote:
> > On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> > wrote:
> >
> >
> > > A group of us at Google have decided to try to implement the RESTful
> > > Data API portion of the Shindig reference implementation with the
> Atom
> > > framework Abdera.
> >
> >
> > It would be good to hold these discussions and make the decisions on
> the
> > mailing list. Decisions made off-channel are generally dangerous for
> apache
> > projects.
> >
> > -Brian
> >
> >
> >
> >
> >
> > > I believe this has been called the 'gateway server'.
> > > We will implement whatever is decided on at
> > > http://groups.google.com/group/opensocial-and-gadgets-spec.
> > >
> > > We are hoping there will be an initial draft spec posted there soon.
> > > Still, we can start now, before the wire formats are finalized, by
> > > getting the basic servlets going and establish a place for people to
> > > try out features. I wanted to send this initial message to the list
> to
> > > let everyone know our intentions and start a discussion of what we
> > > plan on doing. We have a few months experience using Abdera and with
> > > the 0.4 release coming soon, now is a perfect time to kick off this
> > > effort.
> > >
> > > davep
> > >
> > > reference links:
> > > http://incubator.apache.org/abdera/
> > > http://code.google.com/apis/opensocial/docs/dataapis.html
> > >
> >
>
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
Hey Brian,
I didn't mean to imply that Google as a company had decided the fate
of the Shindig project in this area. Far from it, my team in Google is
interested in using parts of Shindig and we needed an API server (a
current gap), so thought we'd contribute some code to Shindig.
One reason why it may appear that there was some hidden discussion is
that there also happened to be an open source Java Atom server project
that has been going on at Google since last spring. It uses Abdera
http://code.google.com/p/google-feedserver/. We have been contributing
code to Abdera for the last couple of months and have become familiar
with the codebase. This effort was not coordinated or discussed with
the Shindig list because it was started before OpenSocial / Shindig
was conceived. So we have a situation where some experience was
developed independent of OpenSocial that happened to be applicable.
I hope this helps clarify it. I'm completely willing to discuss pros
and cons of using Abdera. I think it's a very good server and I wanted
to suggest that Shindig use it.
davep
On Mon, Feb 25, 2008 at 7:59 PM, Brian McCallister <br...@skife.org> wrote:
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> wrote:
>
>
> > A group of us at Google have decided to try to implement the RESTful
> > Data API portion of the Shindig reference implementation with the Atom
> > framework Abdera.
>
>
> It would be good to hold these discussions and make the decisions on the
> mailing list. Decisions made off-channel are generally dangerous for apache
> projects.
>
> -Brian
>
>
>
>
>
> > I believe this has been called the 'gateway server'.
> > We will implement whatever is decided on at
> > http://groups.google.com/group/opensocial-and-gadgets-spec.
> >
> > We are hoping there will be an initial draft spec posted there soon.
> > Still, we can start now, before the wire formats are finalized, by
> > getting the basic servlets going and establish a place for people to
> > try out features. I wanted to send this initial message to the list to
> > let everyone know our intentions and start a discussion of what we
> > plan on doing. We have a few months experience using Abdera and with
> > the 0.4 release coming soon, now is a perfect time to kick off this
> > effort.
> >
> > davep
> >
> > reference links:
> > http://incubator.apache.org/abdera/
> > http://code.google.com/apis/opensocial/docs/dataapis.html
> >
>
Re: Shindig RESTful API server implementation
Posted by Brian McCallister <br...@skife.org>.
On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
wrote:
> A group of us at Google have decided to try to implement the RESTful
> Data API portion of the Shindig reference implementation with the Atom
> framework Abdera.
It would be good to hold these discussions and make the decisions on the
mailing list. Decisions made off-channel are generally dangerous for apache
projects.
-Brian
> I believe this has been called the 'gateway server'.
> We will implement whatever is decided on at
> http://groups.google.com/group/opensocial-and-gadgets-spec.
>
> We are hoping there will be an initial draft spec posted there soon.
> Still, we can start now, before the wire formats are finalized, by
> getting the basic servlets going and establish a place for people to
> try out features. I wanted to send this initial message to the list to
> let everyone know our intentions and start a discussion of what we
> plan on doing. We have a few months experience using Abdera and with
> the 0.4 release coming soon, now is a perfect time to kick off this
> effort.
>
> davep
>
> reference links:
> http://incubator.apache.org/abdera/
> http://code.google.com/apis/opensocial/docs/dataapis.html
>
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
On Mon, Feb 25, 2008 at 4:30 PM, Cassie <do...@apache.org> wrote:
>
> It would also be good to have a quick design discussion to see how best this
> could integrate with the java and php versions. I'm not up on php at all so
> perhaps someone who is can comment on how abdera might integrate with
> multiple languages.
I'm not sure how PHP integration would work and I don't know if it
there is a leading REST-y PHP library. The Java-only integration will
be fairly straightforward, however if PHP, Python, Ruby or any other
language runtime that wants to support the REST protocols would have
to go to the projects available in their space.
By the way, there are also other Java frameworks to do APIs, like
restlet and jersey. (I haven't looked at their licensing issues). We
just picked Abdera because it was the most mature at the time we were
looking (last fall).
davep
http://www.restlet.org/
https://jersey.dev.java.net/
>
> Thanks.
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> wrote:
>
>
>
> > A group of us at Google have decided to try to implement the RESTful
> > Data API portion of the Shindig reference implementation with the Atom
> > framework Abdera. I believe this has been called the 'gateway server'.
> > We will implement whatever is decided on at
> > http://groups.google.com/group/opensocial-and-gadgets-spec.
> >
> > We are hoping there will be an initial draft spec posted there soon.
> > Still, we can start now, before the wire formats are finalized, by
> > getting the basic servlets going and establish a place for people to
> > try out features. I wanted to send this initial message to the list to
> > let everyone know our intentions and start a discussion of what we
> > plan on doing. We have a few months experience using Abdera and with
> > the 0.4 release coming soon, now is a perfect time to kick off this
> > effort.
> >
> > davep
> >
> > reference links:
> > http://incubator.apache.org/abdera/
> > http://code.google.com/apis/opensocial/docs/dataapis.html
> >
>
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
On Mon, Feb 25, 2008 at 4:30 PM, Cassie <do...@apache.org> wrote:
>
> It would also be good to have a quick design discussion to see how best this
> could integrate with the java and php versions. I'm not up on php at all so
> perhaps someone who is can comment on how abdera might integrate with
> multiple languages.
I'm not sure how PHP integration would work and I don't know if it
there is a leading REST-y PHP library. The Java-only integration will
be fairly straightforward, however if PHP, Python, Ruby or any other
language runtime that wants to support the REST protocols would have
to go to the projects available in their space.
By the way, there are also other Java frameworks to do APIs, like
restlet and jersey. (I haven't looked at their licensing issues). We
just picked Abdera because it was the most mature at the time we were
looking (last fall).
davep
http://www.restlet.org/
https://jersey.dev.java.net/
>
> Thanks.
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> wrote:
>
>
>
> > A group of us at Google have decided to try to implement the RESTful
> > Data API portion of the Shindig reference implementation with the Atom
> > framework Abdera. I believe this has been called the 'gateway server'.
> > We will implement whatever is decided on at
> > http://groups.google.com/group/opensocial-and-gadgets-spec.
> >
> > We are hoping there will be an initial draft spec posted there soon.
> > Still, we can start now, before the wire formats are finalized, by
> > getting the basic servlets going and establish a place for people to
> > try out features. I wanted to send this initial message to the list to
> > let everyone know our intentions and start a discussion of what we
> > plan on doing. We have a few months experience using Abdera and with
> > the 0.4 release coming soon, now is a perfect time to kick off this
> > effort.
> >
> > davep
> >
> > reference links:
> > http://incubator.apache.org/abdera/
> > http://code.google.com/apis/opensocial/docs/dataapis.html
> >
>
Re: Shindig RESTful API server implementation
Posted by Cassie <do...@apache.org>.
java/social/... contains servlets and related code for serving social data.
This is currently consumed by shindig's implementation of the opensocial-0.7
feature.
For more information about how opensocial and gadgets work together (ie
opensocial is a feature of gadgets) it is probably best to refer to the
opensocial site [1]
As for how shindig works, the social data is simply being fetched from one
servlet: SocialDataServlet
This servlet is currently being served off of the same server in the default
config of shindig (localhost:8080/gadgets/socialdata) but of course can be
separated out into another server simply because it's just a servlet...
For the restful code, because it is specific to the social features of
gadgets, it should probably live within the social directory. (this is what
Kevin was talking about). You will probably just want to add a servlet of
your own into java/social/http called something ingenious like
RestfulApiServlet :)
The abdera specific code may want to live in its own folder, but I'm sure we
can figure it out as we see how the code progresses.
Also, the java/social directory has a lot of code that I hope can be shared
between the servlet implementations. Things like the Person object, the
IdSpec enum, some interfaces for fetching data from a file based backend
(implementation of those not finished) etc.
I hope this answers your questions. I think creating the initial servlet in
that java/social/http directory with some basic infrastructure is probably a
good first patch.
- Cassie
[1] http://code.google.com/apis/opensocial/
On Tue, Feb 26, 2008 at 12:21 PM, David Primmer <da...@gmail.com>
wrote:
> On Mon, Feb 25, 2008 at 4:39 PM, Kevin Brown <et...@google.com> wrote:
> > Put it in java/social (or maybe java/rest or something else if you
> really
> > want to get pedantic) and I think you're fine as long as it doesn't
> conflict
> > with anything else.
>
> I'll take your word for it, but I'm not sure of the meaning of
> java/social. java/gadets is the Shindig Gadget Server I'm assuming. So
> what does social mean here? What else would go in this location
> besides the gateway? Is there a post to the list or a doc somewhere
> that outlines how the project fits together?
>
> thanks.
>
> davep
>
Re: Shindig RESTful API server implementation
Posted by Cassie <do...@apache.org>.
java/social/... contains servlets and related code for serving social data.
This is currently consumed by shindig's implementation of the opensocial-0.7
feature.
For more information about how opensocial and gadgets work together (ie
opensocial is a feature of gadgets) it is probably best to refer to the
opensocial site [1]
As for how shindig works, the social data is simply being fetched from one
servlet: SocialDataServlet
This servlet is currently being served off of the same server in the default
config of shindig (localhost:8080/gadgets/socialdata) but of course can be
separated out into another server simply because it's just a servlet...
For the restful code, because it is specific to the social features of
gadgets, it should probably live within the social directory. (this is what
Kevin was talking about). You will probably just want to add a servlet of
your own into java/social/http called something ingenious like
RestfulApiServlet :)
The abdera specific code may want to live in its own folder, but I'm sure we
can figure it out as we see how the code progresses.
Also, the java/social directory has a lot of code that I hope can be shared
between the servlet implementations. Things like the Person object, the
IdSpec enum, some interfaces for fetching data from a file based backend
(implementation of those not finished) etc.
I hope this answers your questions. I think creating the initial servlet in
that java/social/http directory with some basic infrastructure is probably a
good first patch.
- Cassie
[1] http://code.google.com/apis/opensocial/
On Tue, Feb 26, 2008 at 12:21 PM, David Primmer <da...@gmail.com>
wrote:
> On Mon, Feb 25, 2008 at 4:39 PM, Kevin Brown <et...@google.com> wrote:
> > Put it in java/social (or maybe java/rest or something else if you
> really
> > want to get pedantic) and I think you're fine as long as it doesn't
> conflict
> > with anything else.
>
> I'll take your word for it, but I'm not sure of the meaning of
> java/social. java/gadets is the Shindig Gadget Server I'm assuming. So
> what does social mean here? What else would go in this location
> besides the gateway? Is there a post to the list or a doc somewhere
> that outlines how the project fits together?
>
> thanks.
>
> davep
>
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
On Mon, Feb 25, 2008 at 4:39 PM, Kevin Brown <et...@google.com> wrote:
> Put it in java/social (or maybe java/rest or something else if you really
> want to get pedantic) and I think you're fine as long as it doesn't conflict
> with anything else.
I'll take your word for it, but I'm not sure of the meaning of
java/social. java/gadets is the Shindig Gadget Server I'm assuming. So
what does social mean here? What else would go in this location
besides the gateway? Is there a post to the list or a doc somewhere
that outlines how the project fits together?
thanks.
davep
Re: Shindig RESTful API server implementation
Posted by David Primmer <da...@gmail.com>.
On Mon, Feb 25, 2008 at 4:39 PM, Kevin Brown <et...@google.com> wrote:
> Put it in java/social (or maybe java/rest or something else if you really
> want to get pedantic) and I think you're fine as long as it doesn't conflict
> with anything else.
I'll take your word for it, but I'm not sure of the meaning of
java/social. java/gadets is the Shindig Gadget Server I'm assuming. So
what does social mean here? What else would go in this location
besides the gateway? Is there a post to the list or a doc somewhere
that outlines how the project fits together?
thanks.
davep
Re: Shindig RESTful API server implementation
Posted by Kevin Brown <et...@google.com>.
On Mon, Feb 25, 2008 at 4:30 PM, Cassie <do...@apache.org> wrote:
> It's great that you are going to try to contribute to Shindig, thank you
> for
> your interest!
>
> I would like to put this up to the community though, do we think Shindig
> should start creating scaffolding and eventually implement the in progress
> restful api spec? And if so, should it be on a branch or in the main code
> base?
Put it in java/social (or maybe java/rest or something else if you really
want to get pedantic) and I think you're fine as long as it doesn't conflict
with anything else. As near as I can tell, this can be implemented more or
less without having to affect the gadget server, which ultimately means that
"nobody" using shindig in production will be affected. As your work on the
open social servlets progresses there might be some overlap, but I'd expect
the RESTful APIs to be fully defined by the time that becomes an issue.
Shindig does aim to implement anything necessary to complete the os /
gadgets stack, and it seems to me that this is will ultimately be a
necessary component of that stack.
>
> It would also be good to have a quick design discussion to see how best
> this
> could integrate with the java and php versions. I'm not up on php at all
> so
> perhaps someone who is can comment on how abdera might integrate with
> multiple languages.
>
> Thanks.
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> wrote:
>
> > A group of us at Google have decided to try to implement the RESTful
> > Data API portion of the Shindig reference implementation with the Atom
> > framework Abdera. I believe this has been called the 'gateway server'.
> > We will implement whatever is decided on at
> > http://groups.google.com/group/opensocial-and-gadgets-spec.
> >
> > We are hoping there will be an initial draft spec posted there soon.
> > Still, we can start now, before the wire formats are finalized, by
> > getting the basic servlets going and establish a place for people to
> > try out features. I wanted to send this initial message to the list to
> > let everyone know our intentions and start a discussion of what we
> > plan on doing. We have a few months experience using Abdera and with
> > the 0.4 release coming soon, now is a perfect time to kick off this
> > effort.
> >
> > davep
> >
> > reference links:
> > http://incubator.apache.org/abdera/
> > http://code.google.com/apis/opensocial/docs/dataapis.html
> >
>
--
~Kevin
If you received this email by mistake, please delete it, cancel your mail
account, destroy your hard drive, silence any witnesses, and burn down the
building that you're in.
Re: Shindig RESTful API server implementation
Posted by James Snell <ja...@gmail.com>.
With regards to the PHP implementation, I know there was some work
done last year at IBM on a PHP atompub server implementation. I'm not
sure about the current status of that work, but I can certainly check
to see if the folks who had worked on that would be interested in
contributing some code to the Abdera project -- it's always been our
intention to get other language implementations included.
- James (abdera committer)
On Tue, Feb 26, 2008 at 7:00 AM, Chris Chabot <ch...@xs4all.nl> wrote:
> Abdera is a Java only project, so it's functionality would have re-
> implemented in other languages, or other toolkits could be chosen for
> those languages.
>
> In its self thats not a reason not to use it though, i don't think
> there's any toolkits that could work in both PHP and Java, and as
> David Primmer pointed out, it's a relatively separate from the gadget
> server, so it doesn't impact it's status. It just means that on the
> PHP side i'll have to start from scratch, which would be the case
> anyway :)
>
> -- Chris
>
>
>
> On Feb 26, 2008, at 1:30 AM, Cassie wrote:
>
> > It's great that you are going to try to contribute to Shindig, thank
> > you for
> > your interest!
> >
> > I would like to put this up to the community though, do we think
> > Shindig
> > should start creating scaffolding and eventually implement the in
> > progress
> > restful api spec? And if so, should it be on a branch or in the main
> > code
> > base?
> >
> > It would also be good to have a quick design discussion to see how
> > best this
> > could integrate with the java and php versions. I'm not up on php at
> > all so
> > perhaps someone who is can comment on how abdera might integrate with
> > multiple languages.
> >
> > Thanks.
> >
> > - Cassie
> >
> >
> > On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <david.primmer@gmail.com
> > >
> > wrote:
> >
> >> A group of us at Google have decided to try to implement the RESTful
> >> Data API portion of the Shindig reference implementation with the
> >> Atom
> >> framework Abdera. I believe this has been called the 'gateway
> >> server'.
> >> We will implement whatever is decided on at
> >> http://groups.google.com/group/opensocial-and-gadgets-spec.
> >>
> >> We are hoping there will be an initial draft spec posted there soon.
> >> Still, we can start now, before the wire formats are finalized, by
> >> getting the basic servlets going and establish a place for people to
> >> try out features. I wanted to send this initial message to the list
> >> to
> >> let everyone know our intentions and start a discussion of what we
> >> plan on doing. We have a few months experience using Abdera and with
> >> the 0.4 release coming soon, now is a perfect time to kick off this
> >> effort.
> >>
> >> davep
> >>
> >> reference links:
> >> http://incubator.apache.org/abdera/
> >> http://code.google.com/apis/opensocial/docs/dataapis.html
> >>
>
>
--
- James Snell
http://www.snellspace.com
jasnell@gmail.com
Re: Shindig RESTful API server implementation
Posted by Chris Chabot <ch...@xs4all.nl>.
Abdera is a Java only project, so it's functionality would have re-
implemented in other languages, or other toolkits could be chosen for
those languages.
In its self thats not a reason not to use it though, i don't think
there's any toolkits that could work in both PHP and Java, and as
David Primmer pointed out, it's a relatively separate from the gadget
server, so it doesn't impact it's status. It just means that on the
PHP side i'll have to start from scratch, which would be the case
anyway :)
-- Chris
On Feb 26, 2008, at 1:30 AM, Cassie wrote:
> It's great that you are going to try to contribute to Shindig, thank
> you for
> your interest!
>
> I would like to put this up to the community though, do we think
> Shindig
> should start creating scaffolding and eventually implement the in
> progress
> restful api spec? And if so, should it be on a branch or in the main
> code
> base?
>
> It would also be good to have a quick design discussion to see how
> best this
> could integrate with the java and php versions. I'm not up on php at
> all so
> perhaps someone who is can comment on how abdera might integrate with
> multiple languages.
>
> Thanks.
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <david.primmer@gmail.com
> >
> wrote:
>
>> A group of us at Google have decided to try to implement the RESTful
>> Data API portion of the Shindig reference implementation with the
>> Atom
>> framework Abdera. I believe this has been called the 'gateway
>> server'.
>> We will implement whatever is decided on at
>> http://groups.google.com/group/opensocial-and-gadgets-spec.
>>
>> We are hoping there will be an initial draft spec posted there soon.
>> Still, we can start now, before the wire formats are finalized, by
>> getting the basic servlets going and establish a place for people to
>> try out features. I wanted to send this initial message to the list
>> to
>> let everyone know our intentions and start a discussion of what we
>> plan on doing. We have a few months experience using Abdera and with
>> the 0.4 release coming soon, now is a perfect time to kick off this
>> effort.
>>
>> davep
>>
>> reference links:
>> http://incubator.apache.org/abdera/
>> http://code.google.com/apis/opensocial/docs/dataapis.html
>>
Re: Shindig RESTful API server implementation
Posted by Kevin Brown <et...@google.com>.
On Mon, Feb 25, 2008 at 4:30 PM, Cassie <do...@apache.org> wrote:
> It's great that you are going to try to contribute to Shindig, thank you
> for
> your interest!
>
> I would like to put this up to the community though, do we think Shindig
> should start creating scaffolding and eventually implement the in progress
> restful api spec? And if so, should it be on a branch or in the main code
> base?
Put it in java/social (or maybe java/rest or something else if you really
want to get pedantic) and I think you're fine as long as it doesn't conflict
with anything else. As near as I can tell, this can be implemented more or
less without having to affect the gadget server, which ultimately means that
"nobody" using shindig in production will be affected. As your work on the
open social servlets progresses there might be some overlap, but I'd expect
the RESTful APIs to be fully defined by the time that becomes an issue.
Shindig does aim to implement anything necessary to complete the os /
gadgets stack, and it seems to me that this is will ultimately be a
necessary component of that stack.
>
> It would also be good to have a quick design discussion to see how best
> this
> could integrate with the java and php versions. I'm not up on php at all
> so
> perhaps someone who is can comment on how abdera might integrate with
> multiple languages.
>
> Thanks.
>
> - Cassie
>
>
> On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
> wrote:
>
> > A group of us at Google have decided to try to implement the RESTful
> > Data API portion of the Shindig reference implementation with the Atom
> > framework Abdera. I believe this has been called the 'gateway server'.
> > We will implement whatever is decided on at
> > http://groups.google.com/group/opensocial-and-gadgets-spec.
> >
> > We are hoping there will be an initial draft spec posted there soon.
> > Still, we can start now, before the wire formats are finalized, by
> > getting the basic servlets going and establish a place for people to
> > try out features. I wanted to send this initial message to the list to
> > let everyone know our intentions and start a discussion of what we
> > plan on doing. We have a few months experience using Abdera and with
> > the 0.4 release coming soon, now is a perfect time to kick off this
> > effort.
> >
> > davep
> >
> > reference links:
> > http://incubator.apache.org/abdera/
> > http://code.google.com/apis/opensocial/docs/dataapis.html
> >
>
--
~Kevin
If you received this email by mistake, please delete it, cancel your mail
account, destroy your hard drive, silence any witnesses, and burn down the
building that you're in.
Re: Shindig RESTful API server implementation
Posted by Cassie <do...@apache.org>.
It's great that you are going to try to contribute to Shindig, thank you for
your interest!
I would like to put this up to the community though, do we think Shindig
should start creating scaffolding and eventually implement the in progress
restful api spec? And if so, should it be on a branch or in the main code
base?
It would also be good to have a quick design discussion to see how best this
could integrate with the java and php versions. I'm not up on php at all so
perhaps someone who is can comment on how abdera might integrate with
multiple languages.
Thanks.
- Cassie
On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
wrote:
> A group of us at Google have decided to try to implement the RESTful
> Data API portion of the Shindig reference implementation with the Atom
> framework Abdera. I believe this has been called the 'gateway server'.
> We will implement whatever is decided on at
> http://groups.google.com/group/opensocial-and-gadgets-spec.
>
> We are hoping there will be an initial draft spec posted there soon.
> Still, we can start now, before the wire formats are finalized, by
> getting the basic servlets going and establish a place for people to
> try out features. I wanted to send this initial message to the list to
> let everyone know our intentions and start a discussion of what we
> plan on doing. We have a few months experience using Abdera and with
> the 0.4 release coming soon, now is a perfect time to kick off this
> effort.
>
> davep
>
> reference links:
> http://incubator.apache.org/abdera/
> http://code.google.com/apis/opensocial/docs/dataapis.html
>
Re: Shindig RESTful API server implementation
Posted by Cassie <do...@apache.org>.
It's great that you are going to try to contribute to Shindig, thank you for
your interest!
I would like to put this up to the community though, do we think Shindig
should start creating scaffolding and eventually implement the in progress
restful api spec? And if so, should it be on a branch or in the main code
base?
It would also be good to have a quick design discussion to see how best this
could integrate with the java and php versions. I'm not up on php at all so
perhaps someone who is can comment on how abdera might integrate with
multiple languages.
Thanks.
- Cassie
On Mon, Feb 25, 2008 at 3:12 PM, David Primmer <da...@gmail.com>
wrote:
> A group of us at Google have decided to try to implement the RESTful
> Data API portion of the Shindig reference implementation with the Atom
> framework Abdera. I believe this has been called the 'gateway server'.
> We will implement whatever is decided on at
> http://groups.google.com/group/opensocial-and-gadgets-spec.
>
> We are hoping there will be an initial draft spec posted there soon.
> Still, we can start now, before the wire formats are finalized, by
> getting the basic servlets going and establish a place for people to
> try out features. I wanted to send this initial message to the list to
> let everyone know our intentions and start a discussion of what we
> plan on doing. We have a few months experience using Abdera and with
> the 0.4 release coming soon, now is a perfect time to kick off this
> effort.
>
> davep
>
> reference links:
> http://incubator.apache.org/abdera/
> http://code.google.com/apis/opensocial/docs/dataapis.html
>