Lalaji,
#5) The handlers will catch any request to the social APIs, including REST
requests, JavaScript requests (via a gadget), or RPC requests. This separates
the back-end service from the request mechanism used to interact with the
service (REST, JavaScript, RPC). The handler's service pat
Walter,
To my knowledge, Activity Streams support is not under development for the PHP
stack.
We have a rough document linking sections of the OpenSocial spec to
implementors:
https://docs.google.com/spreadsheet/ccc?key=0AihdZBncP3KzdGN3dVl3MFpIUlk2TXIyR3hfUDhHZUE&hl=en_US#gid=0.
- Eric W.
Hi Eric,
Thanks a lot for your helpful explanation.And yet I'm learning the
Opensocail concepts.Hence I hope if I ask more three questions,it will be
ok.My questions are inline with your comments.
On Thu, Oct 20, 2011 at 12:45 AM, Eric Woods wrote:
> Hi Lalaji,
>
> I'm the primary implementor o
Hi Eric,
Do you have any news on such support for the PHP stack?
Cheers
walter
-Messaggio originale-
Da: Eric Woods [mailto:woods...@gmail.com]
Inviato: mercoledì 19 ottobre 2011 22.15
A: dev@shindig.apache.org
Oggetto: Re: Regarding Open Social 2.0 Implementation in Shindig
Hi Lalaji
Hi Lalaji,
I'm the primary implementor of Activity Streams in Apache Shindig. All of your
questions are good. I'll do my best to address each one:
1) There is no intentional mapping between Activity Streams and OpenSocial's
"Activity" construct. The "Activity" construct largely considered a
Hi Devs,
We are interest of Activity Streaming in Open Social 2.0 and currently we
are looking into your code[Shindig trunk],how you have implemented
ActivityStreaming according to the specification[1].
Though the documentation on how you have implemented opensocial 2.0 in
Shindig is much lower,we
