Re: [Architecture] RESTFul API for App Manager - Design discussion

[Sanjeewa Malalgoda]

Hi Frank, Thilini,
Really sorry that i missed this thread and taking long time to reply.

As i understood this is more like a application implementation level thing
and its not related to authentication and security.
To be clear on this, security, authentication or authorization may depend
on user credentials, access tokens etc.
If we carefully analyze this requirement you need to do some
filtering/checking based on current state of application(not entirely
depend on auth data).
So i think its better to move this to application(web service
implementation). You may take user from message context do service
implementation level checks.

Thanks,
sanjeewa.

On Wed, Apr 27, 2016 at 3:12 PM, Frank Leymann  wrote:

> Sanjeewa (or Prabath) may have guidance on this...
>
>
> Best regards,
> Frank
>
> 2016-04-27 11:11 GMT+02:00 Thilini Shanika :
>
>> + Frank
>>
>> On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika 
>> wrote:
>>
>>> Hi,
>>>
>>> We have a little concern regarding the permission check in OAuth secured
>>> APIs in APPM.
>>>
>>> Currently, all the available APIs are attached with relevant OAuth 2
>>> scopes, but there are some cases where we cannot manage permissions using
>>> scopes only.
>>>
>>> For example, in application lifecycle change API, we need to check user
>>> permissions in different criterias. Required permission to change the
>>> lifecycle state of a mobile/webapp depends on the current state.
>>>  ie: The users with Internal/creator is allowed to perform the lifecycle
>>> action 'Submit for Review' and change the state into 'In-review'. But rest
>>> of the lifecycle state changes are allowed for users with
>>> 'Internal/publisher'.Below is the API definition.
>>>
>>> URL :
>>> http://localhost:9763/api/appm/publisher/v1.0/apps
>>> /{appType}/change-lifecycle
>>> HTTP Methos : POST
>>> URI Params : appId, action (ie: Submit for Review, Approve,
>>> Publish,Reject ..)
>>>
>>> Thus we cannot achieve this permission check by attaching scopes with
>>> the lifecycle change API, since there's a confusion in scope-role mapping.
>>> (Current scope mapping is scope-role mapping : 'appm:publish' --> admin,
>>> Internal/publisher. But this mapping cannot be applied for 'Submit for
>>> Review' state change since its allowed to perform by 'Internal/creator')
>>>
>>>
>>> We have two options to overcome this problem.
>>>
>>>1. Remove scopes from lifecycle change API and manage permission
>>>check in code level
>>>2. Avoid using a common api for all lifecycle changes and maintain
>>>different API resources for different lifecycle actions which require
>>>different permissions. So different scopes can be assigned to each API.
>>>
>>> What would be the best option? You suggestions and comments are highly
>>> appreciated.
>>>
>>> Thanks
>>>
>>> On Tue, Apr 26, 2016 at 7:49 PM, Manuranga Perera  wrote:
>>>
 agreed Gayan.
 If we have following, it will be clearer. I changed 'apps' to '
 installations'

 DELETE http://localhost:9763/api/appm/storeadmin/v1.0/users/
 admin/installations/cec2027d-2dd6-4826-97c5-33be4eb83ae1

 On Tue, Apr 26, 2016 at 12:33 AM, Gayan Gunarathne 
 wrote:

>
>
> On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera 
> wrote:
>
>> DELETE is verb to un-link resources.
>> Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form
>> appM. But it doesn't mean AppM repo will be deleted.
>>
>
> See the url here. That make sense it deletes the starred with
> manu/product-appm.
>
> With the rest, if we define the resources named well, that API is
> intuitive and easy to use. If we defined the resources naming poorly, that
> same API can feel awkward and be difficult to use and understand.
> We need to consider http verb with the resource naming when creating
> the rest api.
>
>
>>
>> [1]
>> https://developer.github.com/v3/activity/starring/#unstar-a-repository
>>
>> On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna <
>> sajit...@wso2.com> wrote:
>>
>>> [+ Frank]
>>>
>>> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <
>>> sajit...@wso2.com> wrote:
>>>
 ... "uninstall" is NOT a REST, even though it looks like REST.

 "uninstall" does not looks like REST. It looks like RPC.

 On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
 wrote:

> I disagree Manu, The point is this is not "DELETE" action on a
> "resource". This is an action to remove a link between two resources. 
> But
> one oth that "Resource" is just a virtual resource(which is not under
> control of the system). So I think having DELETE HTTP verb is wrong 
> in this.
>
> Cheer,

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Frank Leymann]

Sanjeewa (or Prabath) may have guidance on this...


Best regards,
Frank

2016-04-27 11:11 GMT+02:00 Thilini Shanika :

> + Frank
>
> On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika 
> wrote:
>
>> Hi,
>>
>> We have a little concern regarding the permission check in OAuth secured
>> APIs in APPM.
>>
>> Currently, all the available APIs are attached with relevant OAuth 2
>> scopes, but there are some cases where we cannot manage permissions using
>> scopes only.
>>
>> For example, in application lifecycle change API, we need to check user
>> permissions in different criterias. Required permission to change the
>> lifecycle state of a mobile/webapp depends on the current state.
>>  ie: The users with Internal/creator is allowed to perform the lifecycle
>> action 'Submit for Review' and change the state into 'In-review'. But rest
>> of the lifecycle state changes are allowed for users with
>> 'Internal/publisher'.Below is the API definition.
>>
>> URL :
>> http://localhost:9763/api/appm/publisher/v1.0/apps
>> /{appType}/change-lifecycle
>> HTTP Methos : POST
>> URI Params : appId, action (ie: Submit for Review, Approve,
>> Publish,Reject ..)
>>
>> Thus we cannot achieve this permission check by attaching scopes with the
>> lifecycle change API, since there's a confusion in scope-role mapping.
>> (Current scope mapping is scope-role mapping : 'appm:publish' --> admin,
>> Internal/publisher. But this mapping cannot be applied for 'Submit for
>> Review' state change since its allowed to perform by 'Internal/creator')
>>
>>
>> We have two options to overcome this problem.
>>
>>1. Remove scopes from lifecycle change API and manage permission
>>check in code level
>>2. Avoid using a common api for all lifecycle changes and maintain
>>different API resources for different lifecycle actions which require
>>different permissions. So different scopes can be assigned to each API.
>>
>> What would be the best option? You suggestions and comments are highly
>> appreciated.
>>
>> Thanks
>>
>> On Tue, Apr 26, 2016 at 7:49 PM, Manuranga Perera  wrote:
>>
>>> agreed Gayan.
>>> If we have following, it will be clearer. I changed 'apps' to '
>>> installations'
>>>
>>> DELETE http://localhost:9763/api/appm/storeadmin/v1.0/users/
>>> admin/installations/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>>>
>>> On Tue, Apr 26, 2016 at 12:33 AM, Gayan Gunarathne 
>>> wrote:
>>>


 On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera 
 wrote:

> DELETE is verb to un-link resources.
> Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form
> appM. But it doesn't mean AppM repo will be deleted.
>

 See the url here. That make sense it deletes the starred with
 manu/product-appm.

 With the rest, if we define the resources named well, that API is
 intuitive and easy to use. If we defined the resources naming poorly, that
 same API can feel awkward and be difficult to use and understand.
 We need to consider http verb with the resource naming when creating
 the rest api.


>
> [1]
> https://developer.github.com/v3/activity/starring/#unstar-a-repository
>
> On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna <
> sajit...@wso2.com> wrote:
>
>> [+ Frank]
>>
>> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <
>> sajit...@wso2.com> wrote:
>>
>>> ... "uninstall" is NOT a REST, even though it looks like REST.
>>>
>>> "uninstall" does not looks like REST. It looks like RPC.
>>>
>>> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 I disagree Manu, The point is this is not "DELETE" action on a
 "resource". This is an action to remove a link between two resources. 
 But
 one oth that "Resource" is just a virtual resource(which is not under
 control of the system). So I think having DELETE HTTP verb is wrong in 
 this.

 Cheer,
 Ruwan

 On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
 wrote:

> I think, even if it's not immediately affected (asynchronous), you
> still have to use the correct HTTP verb.
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --

 *Ruwan Abeykoon*
 *Architect,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: ruw...@wso2.com

 ___
 Architecture mailing list
 Architecture@wso2.org
 

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Thilini Shanika]

+ Frank

On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika  wrote:

> Hi,
>
> We have a little concern regarding the permission check in OAuth secured
> APIs in APPM.
>
> Currently, all the available APIs are attached with relevant OAuth 2
> scopes, but there are some cases where we cannot manage permissions using
> scopes only.
>
> For example, in application lifecycle change API, we need to check user
> permissions in different criterias. Required permission to change the
> lifecycle state of a mobile/webapp depends on the current state.
>  ie: The users with Internal/creator is allowed to perform the lifecycle
> action 'Submit for Review' and change the state into 'In-review'. But rest
> of the lifecycle state changes are allowed for users with
> 'Internal/publisher'.Below is the API definition.
>
> URL :
> http://localhost:9763/api/appm/publisher/v1.0/apps
> /{appType}/change-lifecycle
> HTTP Methos : POST
> URI Params : appId, action (ie: Submit for Review, Approve,
> Publish,Reject ..)
>
> Thus we cannot achieve this permission check by attaching scopes with the
> lifecycle change API, since there's a confusion in scope-role mapping.
> (Current scope mapping is scope-role mapping : 'appm:publish' --> admin,
> Internal/publisher. But this mapping cannot be applied for 'Submit for
> Review' state change since its allowed to perform by 'Internal/creator')
>
>
> We have two options to overcome this problem.
>
>1. Remove scopes from lifecycle change API and manage permission check
>in code level
>2. Avoid using a common api for all lifecycle changes and maintain
>different API resources for different lifecycle actions which require
>different permissions. So different scopes can be assigned to each API.
>
> What would be the best option? You suggestions and comments are highly
> appreciated.
>
> Thanks
>
> On Tue, Apr 26, 2016 at 7:49 PM, Manuranga Perera  wrote:
>
>> agreed Gayan.
>> If we have following, it will be clearer. I changed 'apps' to '
>> installations'
>>
>> DELETE http://localhost:9763/api/appm/storeadmin/v1.0/users/
>> admin/installations/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>>
>> On Tue, Apr 26, 2016 at 12:33 AM, Gayan Gunarathne 
>> wrote:
>>
>>>
>>>
>>> On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera  wrote:
>>>
 DELETE is verb to un-link resources.
 Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form
 appM. But it doesn't mean AppM repo will be deleted.

>>>
>>> See the url here. That make sense it deletes the starred with
>>> manu/product-appm.
>>>
>>> With the rest, if we define the resources named well, that API is
>>> intuitive and easy to use. If we defined the resources naming poorly, that
>>> same API can feel awkward and be difficult to use and understand.
>>> We need to consider http verb with the resource naming when creating the
>>> rest api.
>>>
>>>

 [1]
 https://developer.github.com/v3/activity/starring/#unstar-a-repository

 On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

> [+ Frank]
>
> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <
> sajit...@wso2.com> wrote:
>
>> ... "uninstall" is NOT a REST, even though it looks like REST.
>>
>> "uninstall" does not looks like REST. It looks like RPC.
>>
>> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
>> wrote:
>>
>>> I disagree Manu, The point is this is not "DELETE" action on a
>>> "resource". This is an action to remove a link between two resources. 
>>> But
>>> one oth that "Resource" is just a virtual resource(which is not under
>>> control of the system). So I think having DELETE HTTP verb is wrong in 
>>> this.
>>>
>>> Cheer,
>>> Ruwan
>>>
>>> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
>>> wrote:
>>>
 I think, even if it's not immediately affected (asynchronous), you
 still have to use the correct HTTP verb.

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> *Ruwan Abeykoon*
>>> *Architect,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: ruw...@wso2.com
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>
>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; 

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Thilini Shanika]

Hi,

We have a little concern regarding the permission check in OAuth secured
APIs in APPM.

Currently, all the available APIs are attached with relevant OAuth 2
scopes, but there are some cases where we cannot manage permissions using
scopes only.

For example, in application lifecycle change API, we need to check user
permissions in different criterias. Required permission to change the
lifecycle state of a mobile/webapp depends on the current state.
 ie: The users with Internal/creator is allowed to perform the lifecycle
action 'Submit for Review' and change the state into 'In-review'. But rest
of the lifecycle state changes are allowed for users with
'Internal/publisher'.Below is the API definition.

URL : http://localhost:9763/api/appm/publisher/v1.0/apps
/{appType}/change-lifecycle
HTTP Methos : POST
URI Params : appId, action (ie: Submit for Review, Approve, Publish,Reject
..)

Thus we cannot achieve this permission check by attaching scopes with the
lifecycle change API, since there's a confusion in scope-role mapping.
(Current scope mapping is scope-role mapping : 'appm:publish' --> admin,
Internal/publisher. But this mapping cannot be applied for 'Submit for
Review' state change since its allowed to perform by 'Internal/creator')


We have two options to overcome this problem.

   1. Remove scopes from lifecycle change API and manage permission check
   in code level
   2. Avoid using a common api for all lifecycle changes and maintain
   different API resources for different lifecycle actions which require
   different permissions. So different scopes can be assigned to each API.

What would be the best option? You suggestions and comments are highly
appreciated.

Thanks

On Tue, Apr 26, 2016 at 7:49 PM, Manuranga Perera  wrote:

> agreed Gayan.
> If we have following, it will be clearer. I changed 'apps' to '
> installations'
>
> DELETE http://localhost:9763/api/appm/storeadmin/v1.0/users/
> admin/installations/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>
> On Tue, Apr 26, 2016 at 12:33 AM, Gayan Gunarathne 
> wrote:
>
>>
>>
>> On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera  wrote:
>>
>>> DELETE is verb to un-link resources.
>>> Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form
>>> appM. But it doesn't mean AppM repo will be deleted.
>>>
>>
>> See the url here. That make sense it deletes the starred with
>> manu/product-appm.
>>
>> With the rest, if we define the resources named well, that API is
>> intuitive and easy to use. If we defined the resources naming poorly, that
>> same API can feel awkward and be difficult to use and understand.
>> We need to consider http verb with the resource naming when creating the
>> rest api.
>>
>>
>>>
>>> [1]
>>> https://developer.github.com/v3/activity/starring/#unstar-a-repository
>>>
>>> On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna >> > wrote:
>>>
 [+ Frank]

 On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

> ... "uninstall" is NOT a REST, even though it looks like REST.
>
> "uninstall" does not looks like REST. It looks like RPC.
>
> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
> wrote:
>
>> I disagree Manu, The point is this is not "DELETE" action on a
>> "resource". This is an action to remove a link between two resources. But
>> one oth that "Resource" is just a virtual resource(which is not under
>> control of the system). So I think having DELETE HTTP verb is wrong in 
>> this.
>>
>> Cheer,
>> Ruwan
>>
>> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
>> wrote:
>>
>>> I think, even if it's not immediately affected (asynchronous), you
>>> still have to use the correct HTTP verb.
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Architect,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ruw...@wso2.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>



 --
 Sajith Janaprasad Ariyarathna
 Software Engineer; WSO2, Inc.;  http://wso2.com/

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> With regards,
>>> *Manu*ranga Perera.

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Manuranga Perera]

agreed Gayan.
If we have following, it will be clearer. I changed 'apps' to '
installations'

DELETE http://localhost:9763/api/appm/storeadmin/v1.0/users/
admin/installations/cec2027d-2dd6-4826-97c5-33be4eb83ae1

On Tue, Apr 26, 2016 at 12:33 AM, Gayan Gunarathne  wrote:

>
>
> On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera  wrote:
>
>> DELETE is verb to un-link resources.
>> Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form
>> appM. But it doesn't mean AppM repo will be deleted.
>>
>
> See the url here. That make sense it deletes the starred with
> manu/product-appm.
>
> With the rest, if we define the resources named well, that API is
> intuitive and easy to use. If we defined the resources naming poorly, that
> same API can feel awkward and be difficult to use and understand.
> We need to consider http verb with the resource naming when creating the
> rest api.
>
>
>>
>> [1]
>> https://developer.github.com/v3/activity/starring/#unstar-a-repository
>>
>> On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna 
>> wrote:
>>
>>> [+ Frank]
>>>
>>> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <
>>> sajit...@wso2.com> wrote:
>>>
 ... "uninstall" is NOT a REST, even though it looks like REST.

 "uninstall" does not looks like REST. It looks like RPC.

 On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
 wrote:

> I disagree Manu, The point is this is not "DELETE" action on a
> "resource". This is an action to remove a link between two resources. But
> one oth that "Resource" is just a virtual resource(which is not under
> control of the system). So I think having DELETE HTTP verb is wrong in 
> this.
>
> Cheer,
> Ruwan
>
> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
> wrote:
>
>> I think, even if it's not immediately affected (asynchronous), you
>> still have to use the correct HTTP verb.
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Sajith Janaprasad Ariyarathna
 Software Engineer; WSO2, Inc.;  http://wso2.com/

>>>
>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Gayan Gunarathne]

On Mon, Apr 25, 2016 at 6:48 PM, Manuranga Perera  wrote:

> DELETE is verb to un-link resources.
> Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form appM.
> But it doesn't mean AppM repo will be deleted.
>

See the url here. That make sense it deletes the starred with
manu/product-appm.

With the rest, if we define the resources named well, that API is intuitive
and easy to use. If we defined the resources naming poorly, that same API
can feel awkward and be difficult to use and understand.
We need to consider http verb with the resource naming when creating the
rest api.


>
> [1] https://developer.github.com/v3/activity/starring/#unstar-a-repository
>
> On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna 
> wrote:
>
>> [+ Frank]
>>
>> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna > > wrote:
>>
>>> ... "uninstall" is NOT a REST, even though it looks like REST.
>>>
>>> "uninstall" does not looks like REST. It looks like RPC.
>>>
>>> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 I disagree Manu, The point is this is not "DELETE" action on a
 "resource". This is an action to remove a link between two resources. But
 one oth that "Resource" is just a virtual resource(which is not under
 control of the system). So I think having DELETE HTTP verb is wrong in 
 this.

 Cheer,
 Ruwan

 On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
 wrote:

> I think, even if it's not immediately affected (asynchronous), you
> still have to use the correct HTTP verb.
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --

 *Ruwan Abeykoon*
 *Architect,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: ruw...@wso2.com

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>
>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Manuranga Perera]

DELETE is verb to un-link resources.
Eg: DELETE /user/starred/manu/product-appm [1] will un-link me form appM.
But it doesn't mean AppM repo will be deleted.

[1] https://developer.github.com/v3/activity/starring/#unstar-a-repository

On Mon, Apr 25, 2016 at 6:55 AM, SajithAR Ariyarathna 
wrote:

> [+ Frank]
>
> On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna 
> wrote:
>
>> ... "uninstall" is NOT a REST, even though it looks like REST.
>>
>> "uninstall" does not looks like REST. It looks like RPC.
>>
>> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon  wrote:
>>
>>> I disagree Manu, The point is this is not "DELETE" action on a
>>> "resource". This is an action to remove a link between two resources. But
>>> one oth that "Resource" is just a virtual resource(which is not under
>>> control of the system). So I think having DELETE HTTP verb is wrong in this.
>>>
>>> Cheer,
>>> Ruwan
>>>
>>> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera 
>>> wrote:
>>>
 I think, even if it's not immediately affected (asynchronous), you
 still have to use the correct HTTP verb.

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> *Ruwan Abeykoon*
>>> *Architect,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: ruw...@wso2.com
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>
>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[SajithAR Ariyarathna]

[+ Frank]

On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna 
wrote:

> ... "uninstall" is NOT a REST, even though it looks like REST.
>
> "uninstall" does not looks like REST. It looks like RPC.
>
> On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon  wrote:
>
>> I disagree Manu, The point is this is not "DELETE" action on a
>> "resource". This is an action to remove a link between two resources. But
>> one oth that "Resource" is just a virtual resource(which is not under
>> control of the system). So I think having DELETE HTTP verb is wrong in this.
>>
>> Cheer,
>> Ruwan
>>
>> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera  wrote:
>>
>>> I think, even if it's not immediately affected (asynchronous), you still
>>> have to use the correct HTTP verb.
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Architect,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ruw...@wso2.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>



-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[SajithAR Ariyarathna]

>
> ... "uninstall" is NOT a REST, even though it looks like REST.

"uninstall" does not looks like REST. It looks like RPC.

On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon  wrote:

> I disagree Manu, The point is this is not "DELETE" action on a "resource".
> This is an action to remove a link between two resources. But one oth that
> "Resource" is just a virtual resource(which is not under control of the
> system). So I think having DELETE HTTP verb is wrong in this.
>
> Cheer,
> Ruwan
>
> On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera  wrote:
>
>> I think, even if it's not immediately affected (asynchronous), you still
>> have to use the correct HTTP verb.
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Ruwan Abeykoon]

I disagree Manu, The point is this is not "DELETE" action on a "resource".
This is an action to remove a link between two resources. But one oth that
"Resource" is just a virtual resource(which is not under control of the
system). So I think having DELETE HTTP verb is wrong in this.

Cheer,
Ruwan

On Mon, Apr 25, 2016 at 10:36 AM, Manuranga Perera  wrote:

> I think, even if it's not immediately affected (asynchronous), you still
> have to use the correct HTTP verb.
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ruw...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Manuranga Perera]

I think, even if it's not immediately affected (asynchronous), you still
have to use the correct HTTP verb.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Ruwan Abeykoon]

>>Can we we something like:

>>DELETE
http://localhost:9763/api/appm/storeadmin/v1.0/users/admin/apps/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>>

-1, This has been discussed that the "uninstall" is NOT a REST, even though
it looks like REST. The "DELETE" should be effected on a resource. However
uninstall action affects the "users device" and is not affected right after
the call. Also the action is accepted, however may or may not effective on
device availability and any other policies.

Cheers,
Ruwan

On Thu, Apr 21, 2016 at 10:09 AM, SajithAR Ariyarathna 
wrote:

> DELETE
>> http://localhost:9763/api/appm/storeadmin/v1.0/users/admin/apps/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>>
> +1
>
> On Thu, Apr 21, 2016 at 1:06 AM, Manuranga Perera  wrote:
>
>> Instead:
>>
>> POST http://localhost:9763/api/appm/storeadmin/v1.0/apps/uninstallation
>> {
>>"type": "user",
>>"typeIds": ["admin"],
>> "appId": "cec2027d-2dd6-4826-97c5-33be4eb83ae1"
>> }
>>
>> Can we we something like:
>>
>> DELETE
>> http://localhost:9763/api/appm/storeadmin/v1.0/users/admin/apps/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>>
>> This is more REST like.
>>
>> On Wed, Apr 20, 2016 at 6:55 AM, Lahiru Cooray  wrote:
>>
>>> Hi all,
>>> Here with I'm sharing the finalized swagger definitions for your
>>> reference.
>>>
>>>
>>>
>>> On Thu, Mar 31, 2016 at 9:15 AM, Lahiru Cooray  wrote:
>>>
 Hi Sanjiva,
 Herewith I have attached the pdf's and yes, we referred the WSO2 REST
 API design guideline doc (attached) and also the APIM REST API design [1]
 as references

 [1] https://docs.wso2.com/display/AM1100/apidocs/publisher/



 On Thu, Mar 31, 2016 at 8:40 AM, Sanjiva Weerawarana 
 wrote:

> Lahiru when sharing Google docs to this public list you need to PDF
> and attach as well .. non-WSO2 people can't read this.
>
> I assume this is compatible with the REST API design guidelines doc we
> wrote right?
>
> On Wed, Mar 30, 2016 at 10:06 AM, Lahiru Cooray 
> wrote:
>
>> Hi All,
>>
>> We are planing to implement a RESTFul API to expose the App Manager
>> functionality. Initially we are focussing on replacing AppM Mobile API's
>> (Store/Publisher) .
>> Please refer the proposed new set of API's design [1] (and comparison
>> with existing API's [2]) and comment your suggestions
>>
>> [1]
>> https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
>> [2]
>> https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, CEO & Chief Architect; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; office: (+1 650 745 4499 | +94  11 214 5345)
> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 *Lahiru Cooray*
 Software Engineer
 WSO2, Inc.;http://wso2.com/
 lean.enterprise.middleware

 Mobile: +94 715 654154

>>>
>>>
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ruw...@wso2.com
___
Architecture mailing list
Architecture@wso2.org

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Udara Liyanage]

On Wed, Apr 20, 2016 at 12:36 PM, Manuranga Perera  wrote:

> Instead:
>
> POST http://localhost:9763/api/appm/storeadmin/v1.0/apps/uninstallation
> {
>"type": "user",
>"typeIds": ["admin"],
> "appId": "cec2027d-2dd6-4826-97c5-33be4eb83ae1"
> }
>
> Can we we something like:
>
> DELETE
> http://localhost:9763/api/appm/storeadmin/v1.0/users/admin/apps/cec2027d-2dd6-4826-97c5-33be4eb83ae1
>
> This is more REST like.
>
+1 having actions in url is not REST way.

>
> On Wed, Apr 20, 2016 at 6:55 AM, Lahiru Cooray  wrote:
>
>> Hi all,
>> Here with I'm sharing the finalized swagger definitions for your
>> reference.
>>
>>
>>
>> On Thu, Mar 31, 2016 at 9:15 AM, Lahiru Cooray  wrote:
>>
>>> Hi Sanjiva,
>>> Herewith I have attached the pdf's and yes, we referred the WSO2 REST
>>> API design guideline doc (attached) and also the APIM REST API design [1]
>>> as references
>>>
>>> [1] https://docs.wso2.com/display/AM1100/apidocs/publisher/
>>>
>>>
>>>
>>> On Thu, Mar 31, 2016 at 8:40 AM, Sanjiva Weerawarana 
>>> wrote:
>>>
 Lahiru when sharing Google docs to this public list you need to PDF and
 attach as well .. non-WSO2 people can't read this.

 I assume this is compatible with the REST API design guidelines doc we
 wrote right?

 On Wed, Mar 30, 2016 at 10:06 AM, Lahiru Cooray 
 wrote:

> Hi All,
>
> We are planing to implement a RESTFul API to expose the App Manager
> functionality. Initially we are focussing on replacing AppM Mobile API's
> (Store/Publisher) .
> Please refer the proposed new set of API's design [1] (and comparison
> with existing API's [2]) and comment your suggestions
>
> [1]
> https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
> [2]
> https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Sanjiva Weerawarana, Ph.D.
 Founder, CEO & Chief Architect; WSO2, Inc.;  http://wso2.com/
 email: sanj...@wso2.com; office: (+1 650 745 4499 | +94  11 214 5345)
 x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
 blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
 Lean . Enterprise . Middleware

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Manuranga Perera]

Instead:

POST http://localhost:9763/api/appm/storeadmin/v1.0/apps/uninstallation
{
   "type": "user",
   "typeIds": ["admin"],
"appId": "cec2027d-2dd6-4826-97c5-33be4eb83ae1"
}

Can we we something like:

DELETE
http://localhost:9763/api/appm/storeadmin/v1.0/users/admin/apps/cec2027d-2dd6-4826-97c5-33be4eb83ae1

This is more REST like.

On Wed, Apr 20, 2016 at 6:55 AM, Lahiru Cooray  wrote:

> Hi all,
> Here with I'm sharing the finalized swagger definitions for your reference.
>
>
>
> On Thu, Mar 31, 2016 at 9:15 AM, Lahiru Cooray  wrote:
>
>> Hi Sanjiva,
>> Herewith I have attached the pdf's and yes, we referred the WSO2 REST API
>> design guideline doc (attached) and also the APIM REST API design [1] as
>> references
>>
>> [1] https://docs.wso2.com/display/AM1100/apidocs/publisher/
>>
>>
>>
>> On Thu, Mar 31, 2016 at 8:40 AM, Sanjiva Weerawarana 
>> wrote:
>>
>>> Lahiru when sharing Google docs to this public list you need to PDF and
>>> attach as well .. non-WSO2 people can't read this.
>>>
>>> I assume this is compatible with the REST API design guidelines doc we
>>> wrote right?
>>>
>>> On Wed, Mar 30, 2016 at 10:06 AM, Lahiru Cooray 
>>> wrote:
>>>
 Hi All,

 We are planing to implement a RESTFul API to expose the App Manager
 functionality. Initially we are focussing on replacing AppM Mobile API's
 (Store/Publisher) .
 Please refer the proposed new set of API's design [1] (and comparison
 with existing API's [2]) and comment your suggestions

 [1]
 https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
 [2]
 https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing

 --
 *Lahiru Cooray*
 Software Engineer
 WSO2, Inc.;http://wso2.com/
 lean.enterprise.middleware

 Mobile: +94 715 654154

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, CEO & Chief Architect; WSO2, Inc.;  http://wso2.com/
>>> email: sanj...@wso2.com; office: (+1 650 745 4499 | +94  11 214 5345)
>>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Lahiru Cooray]

Hi all,
Here with I'm sharing the finalized swagger definitions for your reference.



On Thu, Mar 31, 2016 at 9:15 AM, Lahiru Cooray  wrote:

> Hi Sanjiva,
> Herewith I have attached the pdf's and yes, we referred the WSO2 REST API
> design guideline doc (attached) and also the APIM REST API design [1] as
> references
>
> [1] https://docs.wso2.com/display/AM1100/apidocs/publisher/
>
>
>
> On Thu, Mar 31, 2016 at 8:40 AM, Sanjiva Weerawarana 
> wrote:
>
>> Lahiru when sharing Google docs to this public list you need to PDF and
>> attach as well .. non-WSO2 people can't read this.
>>
>> I assume this is compatible with the REST API design guidelines doc we
>> wrote right?
>>
>> On Wed, Mar 30, 2016 at 10:06 AM, Lahiru Cooray  wrote:
>>
>>> Hi All,
>>>
>>> We are planing to implement a RESTFul API to expose the App Manager
>>> functionality. Initially we are focussing on replacing AppM Mobile API's
>>> (Store/Publisher) .
>>> Please refer the proposed new set of API's design [1] (and comparison
>>> with existing API's [2]) and comment your suggestions
>>>
>>> [1]
>>> https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
>>> [2]
>>> https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, CEO & Chief Architect; WSO2, Inc.;  http://wso2.com/
>> email: sanj...@wso2.com; office: (+1 650 745 4499 | +94  11 214 5345)
>> x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
>> blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
>> Lean . Enterprise . Middleware
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>



-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154


publisher-api.yaml
Description: Binary data


store-api.yaml
Description: Binary data


storeadmin-api.yaml
Description: Binary data
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] RESTFul API for App Manager - Design discussion

[Sanjiva Weerawarana]

Lahiru when sharing Google docs to this public list you need to PDF and
attach as well .. non-WSO2 people can't read this.

I assume this is compatible with the REST API design guidelines doc we
wrote right?

On Wed, Mar 30, 2016 at 10:06 AM, Lahiru Cooray  wrote:

> Hi All,
>
> We are planing to implement a RESTFul API to expose the App Manager
> functionality. Initially we are focussing on replacing AppM Mobile API's
> (Store/Publisher) .
> Please refer the proposed new set of API's design [1] (and comparison with
> existing API's [2]) and comment your suggestions
>
> [1]
> https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
> [2]
> https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, CEO & Chief Architect; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; office: (+1 650 745 4499 | +94  11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] RESTFul API for App Manager - Design discussion

[Lahiru Cooray]

Hi All,

We are planing to implement a RESTFul API to expose the App Manager
functionality. Initially we are focussing on replacing AppM Mobile API's
(Store/Publisher) .
Please refer the proposed new set of API's design [1] (and comparison with
existing API's [2]) and comment your suggestions

[1]
https://docs.google.com/a/wso2.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit?usp=sharing
[2]
https://docs.google.com/a/wso2.com/document/d/1aib1gJHCwrpRhp6jNeKfD5KRgldbl_cHf9q9zVi0vTc/edit?usp=sharing

-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture