Hi Jo,
On Wed, Feb 10, 2016 at 8:34 AM, Joseph Fonseka <[email protected]> wrote:
> Hi Sam
>
> Few thought related to notification.
>
> 1. As I see notification can be a more generic use case not specific to
> notifying new API versions.
> Ex. Notify when a new API is added.
>
Is this really needed? IMO, we should not do this.
The reason is that, IMO, all the users will not have a need to know about
the new APIs that are added. Even if we allow them to choose whether to get
notifications on new APIs, it is not useful practically.
Users will subscribe and use APIs based on their use-case and for an end
user, having a new API will not make them change their use-case and
re-implement what they have done. If a user needs a new API and a set of
new features, he/she would come to the store and search for a particular
API that matches their needs.
Notify when subscription is blocked.
>
IMO, this is also not practical. If we are to do this, then we need to
have a mechanism of determining when to send an alert to the and to whom
should we send the alert saying that their subscription is blocked.
Currently if the subscription is blocked, then we anyhow send that in the
response message.
Thanks,
Janaka
> Notify throttling limit reach.
> Notify when action related to workflow is performed.
> etc..
> Thus when developing the notification component we should keep provision
> to support above.
>
> 2. As Amila pointed out we should provide an option to enable / disable
> notifications based on subscriber preference.
>
> Thanks & Regards
> Jo
>
>
>
>
>
> On Wed, Feb 10, 2016 at 2:00 AM, Amila De Silva <[email protected]> wrote:
>
>> Hi Sam,
>>
>> Will the notification be pushed to all the Subscribers of an API, or does
>> the Subscriber have an option to select for which APIs they should be
>> receiving notifications for?
>>
>> On Tue, Feb 9, 2016 at 7:26 PM, Sam Sivayogam <[email protected]> wrote:
>>
>>> Hi All,
>>>
>>> Currently in APIM when a publisher makes a new version of an existing
>>> api there is no OTB solution to notify the existing subscibers.
>>>
>>> Since there is requirement for this, we planned to introuduce a
>>> Notification Feature in the coming APIM release. This Feature will help the
>>> publishers to send a notification message to the existing subscribers; when
>>> they are making a new copy of an existing API. since most users prefer
>>> notifications to be sent through email, we will provide a default
>>> implementation which will notify the subscribers through email.
>>>
>>> What we are planning to do
>>>
>>> 1. Create a EmailNotifier class which will send notification emails to
>>> the existing subscribers.
>>> 2. Provide a Notifier interface which will help the publishers to create
>>> their own Notification implementations according to their requirements such
>>> as SMSNotification.
>>> 3. Create a admin dashboard page to add email configurations, these
>>> configurations will be saved in a registry and will be used by EmailNotifier
>>> 4. Add an option to select the Notify subscribers in the API copying page
>>> 5. Planning to Implement the EmailNotifier class using JAVA Mail API[1]
>>>
>>> Any suggestions and thoughts are highly appreciated.
>>>
>>> [1] http://www.oracle.com/technetwork/java/faq-135477.html#1
>>>
>>> --
>>> *Sam Sivayogam*
>>>
>>> Software Engineer
>>> Mobile : +94 772 906 439
>>> Office : +94 112 145 345
>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>> lean.enterprise.middleware.
>>>
>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * <http://lk.linkedin.com/in/rumeshbandara>*
>
>
--
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com
*E-mail: [email protected] <http://wso2.com>**M: **+94 718370861*
Lean . Enterprise . Middleware
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
