Re: Question regarding appId in ActivityHandler

[Cassie <do...@google.com>]

I'm back now :)

So, if you look at the appdata restful urls you will see that the appId you
are fetching data for is encoded inside the url, like this:
"/people/{userId}/{groupId}/{appId}"

Activities in OpenSocial also have a concept of the app they belong to which
means that the appId should also be inside the url. Unfortunately, this
looks like an oversight in the spec because the appId was not included. I
hope to get this discrepancy resolved by the spec list so that the comment
can be fixed or removed.

I hope that clears things up!

- Cassie


On Wed, Jun 25, 2008 at 8:50 AM, Chris Chabot <ch...@xs4all.nl> wrote:

> yea that was my initial reaction too.
>
> Shame cassie is away on holiday, i think she's the one that wrote that
> comment :)
>
>
> On Jun 25, 2008, at 5:41 PM, Ropu wrote:
>
>  arent we taking the appId from the SecToken right now?
>>
>> ropu
>>
>> On Tue, Jun 24, 2008 at 9:50 PM, Gonzalo Aune <go...@gmail.com>
>> wrote:
>>
>>  Hi everyone,
>>>
>>> i was working hard on the port of the REST API (batchJson request) from
>>> Java
>>> to PHP, and i found this TODO comment in ActivityHandler.java:
>>>
>>> // TODO: The appId should come from the url. The spec needs to be fixed!
>>> private static final String ACTIVITY_ID_PATH =
>>> "/activities/{userId}/{groupId}/{activityId}";
>>> private static final String GROUP_PATH =
>>> "/activities/{userId}/{groupId}/{appId}"; // Note: not what the spec says
>>>
>>> used later in the handlePost method, so what will happen with the "appId"
>>> ?
>>>
>>> Thanks!
>>>
>>> G.-
>>>
>>>
>>
>>
>> --
>> .-. --- .--. ..-
>> R  o  p  u
>>
>
>