Hi all, So there are two parts related to this work.
1. Improving the Store itself to make use of the existing notification capabilities and extend it further for it to be more user friendly. SameeraJ is working on that. 2. The second part is to build the notification capabilities we want for Service Governance. This is typically what Heshani should be looking at. So, let me focus on that. Firstly, before thinking about the UIs involved and how to improve them, we need to think on what types of roles/groups of people would find it useful to have these notification capabilities. This also would help us determine their preferences as to whether an e-mail or a live-update in the system is going to be more useful. Next, not everybody might be interested in getting notified. So, just like we subscribe to consume an API, we need to subscribe to recieve a notification. Since the term subscribe can end up being a little confusing, we need to think about the best ways of combining or separating these two things. Also, the user of the Service Store is not an end-user, but an internal user, or someone who wants to get an understanding about the state of the running service. The word consumer means that they always use a service. This is true for those who consume APIs, but for services, I'm not sure whether that's the right term. So, as you might understand, before getting into the actual implementation details, we need to identify who is going to benefit out of these features and then start explaining requirements in terms of what they want to achieve. We can then decide on how and where to place these things. Thanks, Senaka. On Fri, Aug 1, 2014 at 9:21 AM, Subash Chaturanga <sub...@wso2.com> wrote: > Hi Ruchira, > +1 for sync up. We planned to push this by 5.0.0-M2. It will be end of > this month. > > > On Fri, Aug 1, 2014 at 12:36 PM, Ruchira Wageesha <ruch...@wso2.com> > wrote: > >> Hi Heshani, >> >> If you can get the API ready initially, I think that would be the way. >> Then, from ES store and publisher side, we can use that API to >> send/retrieve notifications. >> >> @Subash, Heshani, >> >> What would be the timeline of this? Sameeraj has already started >> implementing notification support for ES. Hence, we need to sync up with >> you guys. >> >> /Ruchira >> >> >> On Fri, Aug 1, 2014 at 11:33 AM, Heshani Gamage <hesh...@wso2.com> wrote: >> >>> Hi Senaka et. al, >>> >>> I'm implementing $Subject corresponding to the RM[1] .I would like to >>> verify requirements of this feature on following use cases. >>> a. Provide notification support for the Consumer side and Provider Side >>> b. Support for notifications explicitly initiated from the provider to >>> a specific consumer/consumers >>> -For example after a certain bug fix, provider will explicitly notify a >>> certain set of consumers >>> >>> I need clarify following things >>> 1. How should the notification views be displayed on publisher and >>> store? >>> 2. What do we actually mean by a consumer/how should we identify the >>> consumer? (e.g.: e-mail address etc.) >>> 3. How to select specific consumers for b. above? >>> 4. From where should the provider initiate the notification in the b. >>> above >>> 5. As we already have notifications in G-Reg for a certain >>> extent, should display these notifications on the provider side too? >>> >>> >>> Is there anything to be added to the above? >>> >>> [1] https://redmine.wso2.com/issues/2342 >>> >>> Thanks, >>> Heshani >>> >>> -- >>> Heshani Gamage >>> Software Engineer, WSO2, Inc. >>> email : hesh...@wso2.com >>> >> >> >> >> -- >> >> *Ruchira Wageesha**Associate Technical Lead* >> *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* >> >> *email: ruch...@wso2.com <ruch...@wso2.com>, blog: >> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >> mobile: +94 77 5493444 <%2B94%2077%205493444>* >> > > > > -- > Thanks > /subash > > *Subash Chaturanga* > Senior Software Engineer & Lead WSO2 Governance Registry > Platform TG; WSO2 Inc. http://wso2.com > Contact: > email: sub...@wso2.com > blog: http://subashsdm.blogspot.com/ > twitter: @subash89 > phone: +9477 2225922 > Lean . Enterprise . Middleware > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
