Hi.

I think the Basics are well covered in the Readme and source code; but
I'd really enjoy more doc on the Intermediate-Advanced part.
Particularly the RPC mecanism is obscure, because it does not appear
anywhere in the empirical learning path: from the SampleContainer the
natural jump is towards the  BasicServices of the opensocial part, and
the uses of the RPC are not seen.

In fact for http/xml requests beyond the static BasicServices, we
could provide some extra example, along the lines of the
samplecontainer too.

Alejandro

2008/4/3, Christian Schalk <[EMAIL PROTECTED]>:
> 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