I may be not as familiar with the API's already available, but as part
of the API server project, I'm hoping to solve this with a recently
developed way of connecting a native data source backend to the API
server. Abdera has the concept of a CollectionAdapter, which is an
object container that has a CRUD HTTP interface. It leaves to the
developer to choose a backend object mapping system -- the adapter
type. These adapters have the ability to use many different kinds of
data sources as their backing store.

>From the perspective of the 3 APIs in the spec. It will be fairly
straightforward to connect to a native data source. In the typical
case of a database that supports JDBC, an Ibatis XML field mapping
file is filled out and the work is done. No coding.

I don't know if this is the data that you're concerned with here or if
it is something else.

davep

On Wed, Apr 2, 2008 at 4:50 PM, Christian Schalk <[EMAIL PROTECTED]> wrote:
> Hello shindig-dev,
>
>  It seems like a lot of the questions on shindig-dev are around how to wire
>  the OpenSocal API to a real backend. Given that, I'm in the process of
>  putting together a guide on how to attach your local version of Shindig to a
>  native datasource.
>
>  Here's a draft set of items that I'm planning to cover in the guide:
>
>  Basics
>
>
>    1. Quick review on how to install Shindig on your server.
>       - Testing some simple (non-OpenSocial) Gadgets on your server.
>       2. Testing an OpenSocial app within your Shindig environment
>       - Trying out the SampleContainer.
>       - Trying out some other simple OpenSocial apps with the
>       SampleContainer
>       - Playing around with simple XML based state data within the
>       SampleContainer
>
>
>  Intermediate-Advanced
>
>
>    1. State Data access concepts
>    - Reviewing concepts on how to access data
>          - The all Java approach - implementing interfaces
>          - The RPC approach - creating http based response
>          mechanisms
>       2. Building your own data access using either
>       - Java approach
>          - Getting familiar with the classes and interfaces in
>          org.apache.shindig.social.*.
>          - Implement the provided interfaces to access custom data.
>          - Language neutral RPC approach
>          - How to build your own http mechanism in PHP to serve
>          social data
>
>
>  Let me know if you any suggestions or additions, and we'll continue to flesh
>  this out and publish it.
>
>  Thanks,
>  -Chris
>
>  --
>  Chris Schalk, Google Developer Advocate
>

Reply via email to