 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
16 messages in org.apache.incubator.shindig-devRe: proposal for an implementation of...| From | Sent On | Attachments |
|---|---|---|
| Jun Yang (杨骏) | Apr 9, 2008 11:55 am | |
| Jun Yang (杨骏) | Apr 9, 2008 1:01 pm | |
| Jun Yang (杨骏) | Apr 9, 2008 1:01 pm | |
| Jun Yang (杨骏) | Apr 9, 2008 1:48 pm | |
| Kevin Brown | Apr 9, 2008 2:05 pm | |
| Daniel Danger Bentley | Apr 9, 2008 2:08 pm | |
| Kevin Brown | Apr 9, 2008 2:20 pm | |
| Cassie | Apr 10, 2008 4:39 am | |
| Cassie | Apr 10, 2008 4:40 am | |
| Changshin Lee | Apr 10, 2008 5:15 am | |
| David Primmer | Apr 10, 2008 9:29 am | |
| John Panzer | Apr 10, 2008 9:57 am | |
| James M Snell | Apr 10, 2008 10:40 am | |
| David Primmer | May 5, 2008 6:00 pm | |
| John Panzer | May 6, 2008 5:45 pm | |
| Paul Walker | May 9, 2008 1:03 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: proposal for an implementation of OpenSocial RESTful API | Actions... |
|---|---|---|
| From: | Cassie (do...@google.com) | |
| Date: | Apr 10, 2008 4:40:48 am | |
| List: | org.apache.incubator.shindig-dev | |
Oh and I'm bccing the spec mailing list - implementation discussions don't take place on the spec list.
- Cassie
2008/4/10 Cassie <do...@google.com>:
I think rest should == social because they will essentially be the same server. I don't have time to code it right now though, so the patch looks fine and ill draw up another patch for merging the two next week.
- Cassie
2008/4/9 Kevin Brown <et...@google.com>:
Yeah, that looks right -- does maven tolerate dashes, though?
2008/4/9 Daniel Danger Bentley <dtbe...@gmail.com>:
https://issues.apache.org/jira/browse/SHINDIG-174 should be step-1 (or maybe step-.5 on this).
You alright with me checking this in?
2008/4/9 Kevin Brown <et...@google.com>:
Hey Jun,
The first thing you're going to need to do is set up a new sub project
for the RESTful stuff. The correct location would be trunk/java/rest probably (pick whatever name you like).
For the time being, feel free to just directly import the gadgets
artifacts into the REST project until we get the shared parts (OAuth, crypto, app data interfaces, etc.) moved out into a separate sub-project.
We'll need to ensure that the top level pom can generate all appropriate
artifacts as well, so that someone can easily use just the restful api, just the gadget renderer, or both.
On Wed, Apr 9, 2008 at 11:56 AM, Jun Yang (杨骏) <jya...@google.com> wrote:
Hi all.
We would like to propose an implementation for "A modest proposal for an OpenSocial RESTful API".
We propose the following:
Use Apache Abdera as the basis of the reference server implementation Add a JsonCParser to support input in JSON-c format (JSON-c for compact JSON format as specified in the API spec, not a new MIME type) Add a JsonCWriter to support output in JSON-c format Add an OpenSocial API (Person, Activity and AppData, Java version
under org.apache.shindig.social.opensocial) adapter to integrate with existing API implementation and keep the same interface on the backend and the client
for the following reasons:
The RESTful API proposal supports a clean and natural JSON format
(JSON-c) as well as AtomPub. Apache Abdera is an open source reference implementation of AtomPub that offers most of the functionality we need. Reusing it seems to be natural choice
Abdera already supports input in Atom. We need to add support for input in JSON-c Abdera already supports output in Atom (as well as a JSON format). We need to add support for output in JSON-c Abdera's support for adapters that translate from a foreign data
format and protocol into its Feed Object Model (FOM) comes handy to support existing data sources such as relational databases and existing implementation of OpenSocial APIs. Existing OpenSocial APIs are very close to Atom's model and can be adapted easily
We have includes two diagrams as illustration of the architecture of
the proposed implementation. Diagram 1 shows the generic architecture. Those components in italics are to be written. Diagram 2 shows the use of two adapters, iBATIS (existing in Abdera) to integrate with relational databases, and OpenSocial API adapter (to be written), to integrate with existing OpenSocial backend.
Please review and comment. Thanks!
Vasu Nori and Jun Yang
-- ~Kevin
-- 'Ladislav Sticha, the tall spokesman for Czech Television, told me that
the show's audience was "miniature" -- presumably he meant small in number.' - New York Times, January 24, 2008
-- ~Kevin
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group. To post to this group, send email to open...@googlegroups.com To unsubscribe from this group, send email to open...@googlegroups.com For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en -~----------~----~----~----~------~----~------~--~---