Add Notification support to the domain management API

classic Classic list List threaded Threaded
42 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: Add Notification support to the domain management API

Heiko Braun



+1



On Mar 6, 2013, at 2:53 PM, Jeff Mesnil <[hidden email]> wrote:

I see it as a system-wide configuration property.
It's the number of notifications per registered handler (each handler registered through the HTTP has its own buffer of notifications).


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Add Notification support to the domain management API

Jeff Mesnil
In reply to this post by Heiko Braun
I understand why the doc was not clear: I forgot to publish the draft and the public version was the outdated one. Stupid me!

The doc is now correct: https://community.jboss.org/wiki/AddNotificationSupportToTheDomainManagementAPI
 
Le 6 mars 2013 à 08:53, Heiko Braun <[hidden email]> a écrit :

>
> I have some questions regarding your example, where you describe that a notification is emitted (n1) when an attribute value changed and a client (curl) executes two subsequent POST requests (p1, p2) to fetch notifications.
>
> I am wondering what the semantics are for processing/delivering notifications. What can clients expect?
>
> - Stream of notifications: Clients get to see what exists at a given point in time. There is the possibility to miss notifications.
>
> - Durable subscriptions: Regardless of a clients availability and polling interval, it will always get all notifications since the last time it connected. It's not possible to miss notifications.
>
> - Time windows: Notifications are kept for a certain amount of time, during that interval clients get the same snapshot, regardless how many times they poll? It's possible to miss notifications if the polling frequency is much bigger then the window size.
>
>
> Regards, Heiko
>
> On Mar 5, 2013, at 6:11 PM, Jeff Mesnil <[hidden email]> wrote:
>
>> I've updated the documentation about adding notification to AS7[1]
>>
>> I think I've defined the most important parts that clients needs to know to deal with AS7 notifications:
>>
>> * describe notifications in AS7 resource model
>> * define global notifications supported by all resources
>> * AS7 service to register/unregister local listener + emit notifications
>> * HTTP API
>> * plain HTTP with polling notifications
>> * Web-browser specific to push notifications using Server-sent events
>> * extra methods to the Java management API to register/unregister listeners in Java clients
>>
>> Note the doc does not define all the notifications that can be emitted by AS7 resources.
>> The idea is that the AS7 resource model describes them (like attributes and operations) so that the client can use the description to know which resources emit notifications (and their types).
>>
>> jeff
>>
>> [1] https://community.jboss.org/wiki/AddNotificationSupportToTheDomainManagementAPI
>>
>> --
>> Jeff Mesnil
>> JBoss, a division of Red Hat
>> http://jmesnil.net/
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>

--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/


_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
123