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, 24 May 2011 20:21:47 GMT

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

Kurt T Stam commented on JUDDI-423:
-----------------------------------

Notifications are only sent if there are actual changes in the registry. I've taken the time
to review the code and made sure this is so. Also we are collecting statistics on publish
method invocations, and these statistics are used to prevent running unnecessary queries to
the database. The code is the shared by all entities (not just services).

> 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.1.0
>
>
> 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 5.5.8.2). 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message