Hi All,
The meeting notes are as follows,
Sorting
- Remove multiple parameter support for sorting
</asset/gadgets?sort=+overview_name,-overview_provider>
- Only sorting by one parameter will be supported
*Pagination*
- Users can handle pagination manually
- Limit the ‘count’ for a max value
- How can we define the number of pages in pagination? Do we get the
total number of items? What if the data set is very large?
- This should be decided based on researching how pagination is done and
what Registry supports
*Field expansion*
- Use this to limit the amount of data retrieved through an API call
*Properties*
- Make ‘singular/plural name’ available through field expansion; only
ask for when needed
- Singular/plural names has to be injected tothe asset object
- Make properties optional by expansion
- The singularName and pluralName has to be injected to the asset
object. Is it useful?
- They are properties at RXT level. What such properties are we
supporting?
- Do we drop ratings/tags when returning an asset object?
*Type*
- search => returns assets, therefore use assets?type=gadget for asset
retrieval
- Change assets/:type to /assets?type=<type>
- This change is required because of requirement of differentiating
/type and /id in assets/:type and assets/:id
- What's more important in single rxt store and multiple rxt store?
- types/ endpoint -- is a must to list types, because it is a special
property
- assets/types/:type should be removed
Tags
- /tags --> return all the tags
- /tags/type= gadget --> returns tags for specified type
- tags/:tagname --> Does this return all assets with the given tag?
Search
- For advance search,
*asset?q=”ovrview_name:”...”,ovrview_provider:”..."*
- Can there be “type”, "start" and "count" as fields of an asset type?
- User defined fields are labeled as *<table-name>_<field-name>* i.e:
*overview_count. *Therefore no conflicts will occur.
*Lifecycle*
- /assets/:id/lifecycle is required to get the lifecycle for a
particular item
- Need /type/lifecycle to return lifecycle associated with a particular
asset type
- Use expansion
/asset/:id/lifecycle/{expansion}
- Provide POST method for this endpoint to execute lifecycle action
- The request and response should be more explained in the document with
samples
- Lifecycle is returned as an attribute when returning a particular
asset through */assets/:id *therefore without returning a large
object(lifecycle definition) with all attributes, use expansion
- /assets/:id/lifecycle/actions, /assets/:id/lifecycle/history,
/assets/:id/lifecycle/comments
- Is using ‘/lifecycle/’ restful?
- It is more of a logical grouping than a resource based grouping
- Action (‘promote’, ‘demote’) is done on the asset, not on the lifecycle
- Would using /asset/:id/actions model instead be better?
- What happens to history when a lifecycle is changed?
- Should we follow the rest way or the performance-wise better way?
*Subscriptions*
- Change endpoint to subscribers from subscriptions. Use
/assets/:id/subscribers instead of /assets/:id/subscriptions
- ‘subscriptions’ is defined as an action on top of an asset. It can be
a custom action for a specific type
- All subscriptions would only be used by admin, a particular user will
only need to retrieve ‘mySubscriptions’
- Return a list of subscriber objects , each containing all
subscriptions by a particular user
- Provide query support for subscribers
- Provide /assets/:id/subscribers/:userid to get subscriptions for a
particular user
- ‘mySubscriptions’ should be provided through a separate endpoint
- Do we provide a POST method for subscribers?
*Versions*
- /assets/:id/versions
- How can we get other versions for a particular asset version as each
version has a different id?
- Are versions for a particular asset tracked by the asset name?
- Can we group versions under id of 1st version or last version?
- If we group them under asset name (bucket) , name should be unique
within a type
- What endpoint should be used to create a new version?
Thank you,
Sameera
On Tue, Jul 22, 2014 at 9:03 AM, Sameera Perera <[email protected]> wrote:
> Hi SameeraJ,
> Can you share the notes please?
>
> SameeraM,
> Please share the doc.
>
>
> On Mon, Jul 21, 2014 at 10:50 AM, Sameera Medagammaddegedara <
> [email protected]> wrote:
>
>> more details »
>> <https://www.google.com/calendar/event?action=VIEW&eid=OXMzanYzNG4zZDUxb2ZmMDlidTkwODZqaTggYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&tok=MTcjc2FtZWVyYW1Ad3NvMi5jb21lZTMwMGUxNmNiYzcwODk4NWFhZTlhMzZmMDJhOTRmNzhjYjUwM2Nh&ctz=Asia/Colombo&hl=en>
>> ES API 2.0.0 Review
>> *When*
>> Mon Jul 21, 2014 11:30am – 12:30pm Colombo
>> *Where*
>> LK 1st Floor Meeting Room (map
>> <http://maps.google.lk/maps?q=LK+1st+Floor+Meeting+Room&hl=en>)
>> *Video call*
>> https://plus.google.com/hangouts/_/wso2.com/sameeram
>> <https://plus.google.com/hangouts/_/wso2.com/sameeram?hceid=c2FtZWVyYW1Ad3NvMi5jb20.9s3jv34n3d51off09bu9086ji8>
>> *Calendar*
>> [email protected]
>> *Who*
>> •
>> Sameera Medagammaddegedara - organizer
>> •
>> Udara Rathnayake
>> •
>> Ruchira Wageesha
>> •
>> Dulitha Wijewantha
>> •
>> Tanya Madurapperuma
>> •
>> [email protected]
>> •
>> Sameera Jayaratna
>> •
>> Ayesha Dissanayaka
>> •
>> Manuranga Perera
>>
>> Going? *Yes
>> <https://www.google.com/calendar/event?action=RESPOND&eid=OXMzanYzNG4zZDUxb2ZmMDlidTkwODZqaTggYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&rst=1&tok=MTcjc2FtZWVyYW1Ad3NvMi5jb21lZTMwMGUxNmNiYzcwODk4NWFhZTlhMzZmMDJhOTRmNzhjYjUwM2Nh&ctz=Asia/Colombo&hl=en>
>> - Maybe
>> <https://www.google.com/calendar/event?action=RESPOND&eid=OXMzanYzNG4zZDUxb2ZmMDlidTkwODZqaTggYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&rst=3&tok=MTcjc2FtZWVyYW1Ad3NvMi5jb21lZTMwMGUxNmNiYzcwODk4NWFhZTlhMzZmMDJhOTRmNzhjYjUwM2Nh&ctz=Asia/Colombo&hl=en>
>> - No
>> <https://www.google.com/calendar/event?action=RESPOND&eid=OXMzanYzNG4zZDUxb2ZmMDlidTkwODZqaTggYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&rst=2&tok=MTcjc2FtZWVyYW1Ad3NvMi5jb21lZTMwMGUxNmNiYzcwODk4NWFhZTlhMzZmMDJhOTRmNzhjYjUwM2Nh&ctz=Asia/Colombo&hl=en>*
>> more options »
>> <https://www.google.com/calendar/event?action=VIEW&eid=OXMzanYzNG4zZDUxb2ZmMDlidTkwODZqaTggYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&tok=MTcjc2FtZWVyYW1Ad3NvMi5jb21lZTMwMGUxNmNiYzcwODk4NWFhZTlhMzZmMDJhOTRmNzhjYjUwM2Nh&ctz=Asia/Colombo&hl=en>
>>
>> Invitation from Google Calendar <https://www.google.com/calendar/>
>>
>> You are receiving this courtesy email at the account
>> [email protected] because you are an attendee of this event.
>>
>> To stop receiving future notifications for this event, decline this
>> event. Alternatively you can sign up for a Google account at
>> https://www.google.com/calendar/ and control your notification settings
>> for your entire calendar.
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> ------------------------------
>
> *Sameera Perera*
> Director of Engineering
> gtalk: [email protected]
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> *WSO2, Inc.* <http://wso2.com/>
> lean.enterprise.middleware
>
>
>
--
*Thanks & Regards,Sameera Jayaratna Software Engineer; **WSO2 Inc. *
*lean . enterprise . middleware | http://wso2.com <http://wso2.com> *
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
