2 messages in com.googlegroups.opensocial-apiRe: Adding support for lifecycle events| From | Sent On | Attachments |
|---|---|---|
| Paul Lindner | 06 Feb 2008 07:07 | |
| ohadpr | 25 Feb 2008 09:37 |
| Subject: | Re: Adding support for lifecycle events |
|---|---|
| From: | ohadpr (oha...@gmail.com) |
| Date: | 02/25/2008 09:37:45 AM |
| List: | com.googlegroups.opensocial-api |
looks like a great spec. i would add some way for the app developer's server to authenticate the call, as in a list of IPs this ping can originate from or a signed message with a known public key.
this should be embraced into open-social, otherwise every app developer or container implementor will have to half-bake a solution.
Ohad Eder Pressman CEO 3D3R Software Studio
On Feb 6, 7:08 am, Paul Lindner <plin...@hi5.com> wrote:
Hi,
Us at hi5 would like to get feedback on a possible mechanism we could use to pass lifecycle events to App writers. We propose that app writers add the following to their gadget xml file:
<Optional feature="x-hi5-opensocial-lifecycle-0.0"/> <Param name="view-remove">http://mysite.com/handleRemove</Param> <Param name="view-add">http://mysite.com/handleAdd</Param> <Param name="resource-exceeded">http://mysite.com/handleNaughty</Param> ... </Optional>
This uses the new <Optional> and <Param> tags in the gadget spec. When each event occurs in the container your backend will receive a ping with some data related to the event. For example adding or removing a gadget would get you the ID of the user and the view -- a resource exhausted warning would give you details on the method that is under restriction and when the restriction will be lifted.
We haven't finalized the ping format or the endpoint names. We'd appreciate comments from app developers on what they think would be worthwhile.
-- Paul Lindner hi5 Architect plin...@hi5.com
application_pgp-signature_part