You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "David Primmer (JIRA)" <ji...@apache.org> on 2008/06/01 08:12:44 UTC
[jira] Created: (SHINDIG-324) Upate the appdata service interface
and samplecontainer BasicDataService to be aware of user id and app id
Upate the appdata service interface and samplecontainer BasicDataService to be aware of user id and app id
----------------------------------------------------------------------------------------------------------
Key: SHINDIG-324
URL: https://issues.apache.org/jira/browse/SHINDIG-324
Project: Shindig
Issue Type: Improvement
Components: RESTful API (Java)
Reporter: David Primmer
Currently, the appdata interface is very simple and doesn't allow user id and app id to be passed in to select entries. In addition to this, it should support getting a single app/user data entity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-324) Upate the appdata service interface
and samplecontainer BasicDataService to be aware of user id and app id
Posted by "David Primmer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601752#action_12601752 ]
David Primmer commented on SHINDIG-324:
---------------------------------------
security token is not the right place for this param. for more info about a entry of appdata, see my post on the spec list regarding problems i'm having with the appdata spec. there is an appdata entry (they're not all collections) and it should be implemented in shindig.
> Upate the appdata service interface and samplecontainer BasicDataService to be aware of user id and app id
> ----------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-324
> URL: https://issues.apache.org/jira/browse/SHINDIG-324
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: David Primmer
>
> Currently, the appdata interface is very simple and doesn't allow user id and app id to be passed in to select entries. In addition to this, it should support getting a single app/user data entity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-324) Upate the appdata service interface
and samplecontainer BasicDataService to be aware of user id and app id
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601748#action_12601748 ]
Cassie Doll commented on SHINDIG-324:
-------------------------------------
It does allow userId and appId to be passed in - the "ids" param is for the user id(s) and the security token contains the app id.
I don't understand what you mean by getting a "single app/user data entity". Can you explain?
> Upate the appdata service interface and samplecontainer BasicDataService to be aware of user id and app id
> ----------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-324
> URL: https://issues.apache.org/jira/browse/SHINDIG-324
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: David Primmer
>
> Currently, the appdata interface is very simple and doesn't allow user id and app id to be passed in to select entries. In addition to this, it should support getting a single app/user data entity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.