juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-423) Asynchronous subscription notification intervals
Date Tue, 26 Oct 2010 16:12:19 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925015#action_12925015

Kurt T Stam commented on JUDDI-423:

We intend to only send out notification when there are changes; just like the 'find_service
notifications' behavior you describe. So you will receive one update. Not one with each interval.
So there seems to be a bug here. It'd be great if you can attach a test, so we reproduce it.
We currently getting ready for a 3.0.4 release and it would be nice to fix this.

Interesting to hear that other products send out the notification with each interval. That
could lead to a lot of useless communication. I think we envision a situation where the interval
can be quite small, so you get near 'real-time' updates of services change.



> Asynchronous subscription notification intervals
> ------------------------------------------------
>                 Key: JUDDI-423
>                 URL: https://issues.apache.org/jira/browse/JUDDI-423
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.3
>         Environment: Apache Tomcat 6.0.29, PostgreSQL 8.4
>            Reporter: Jason Brown
>            Assignee: Kurt T Stam
>            Priority: Minor
>             Fix For: 3.0.4
> When using any asynchronous subscription using a filter other than find_service notifications
are sent regularly at the specified notifcationInterval regardless of whether or not there
is actually a change to the applicable entities. This is not the case when using a find_service
subscriptionFilter, notifications are only sent when changes are made to the applicable entities.
Which of these is the intended behavior? The specification is vague on this issue, stating
in one place that "When asynchronous notifications are requested, subscriptions provide information
on new, changed or deleted entities within a registry that occur after the point in time that
the subscription is registered" (Section 5.5.1) but states that notificationIntervals "specifies
how often change notifications are to be provided to a subscriber." (Section Other
products tend to follow the model jUDDI follows when using a non find_service filter (i.e.
sending a notification at every notificationInterval). 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message