@Madhuka,
Thank you very much for your suggestions.
Hi all,
In an off-line discussion with Ruchira, Manu, SameeraM and myself, we came
to a conclusion on some of ES REST-API endpoints which we were unable to
finalize during the previous meetings.
Finalized endpoints during this discussion are mentioned as follows.
*Life-cycle related Endpoints*
*/lifecycles*
- GET: return list of available life-cycle names
*/lifecycles/<lifecycle-name>*
- GET: return the life cycle definition related to <life-cycle-name>
*/lifecycles/<lifecycle-name>/<state>*
- GET: details (next possible states, check list) bound with the life-cycle
state of <life-cycle-name>
*/assets/:id/state*
- GET: return current-state, next possible states & other related resources
with the current state
- POST: to perform lifecycle action in order to transit to next state
{next state should be sent in the request body}
*/assets/:id/histrory*
- GET: details of life-cycle transitions history and related comments
*Asset Related Endpoints*
*/assets/:id/*comments
*- *GET: available user comments on asset
- POST: post a user comment to asset
On Fri, Jul 25, 2014 at 10:05 AM, madhuka udantha <[email protected]>
wrote:
>
> On Tue, Jul 22, 2014 at 4:45 PM, Sameera Jayaratna <[email protected]>
> wrote:
>
>> Users can handle pagination manually
>> Limit the ‘count’ for a max value
>> How can we define the number of pages in pagination?
>
> This is possible,
> User can define number item for the page,
> Initial call we get total number (count) for our query from registry API
> then build pagination UI on it's callback
>
> For initial item retrieval, you can call with user define count. (adding
> that count for pagination call)
>
>
>> Do we get the total number of items?
>
> You can get the total count (number) via register API
>
> What if the data set is very large?
>> This should be decided based on researching how pagination is done and
>> what Registry supports
>
>
>
>
>
> --
> Cheers,
> Madhuka Udantha
> http://madhukaudantha.blogspot.com
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
20, Palmgrove Avenue, Colombo 3
E-Mail: [email protected] <[email protected]>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
