BIND 10 #2931: Receiving notifications, python part
BIND 10 Development
do-not-reply at isc.org
Fri Apr 26 07:20:08 UTC 2013
#2931: Receiving notifications, python part
-------------------------------------+-------------------------------------
Reporter: | Owner:
vorner | Status: new
Type: task | Milestone: New Tasks
Priority: | Keywords:
medium | Sensitive: 0
Component: | Sub-Project: Core
Inter-module communication | Estimated Difficulty: 0
CVSS Scoring: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
This is part of #1915.
The goal here is to allow receiving notifications. The module session
would get two new methods:
* `registerNotificationCallback(notificationGroup, callback)` ‒ it would
subscribe to a group `Notifications/<notificationGroup>` (if it wasn't
subscribed already), store the callback to be called whenever a
notification comes through that group and return some kind of ID of the
callback.
* `unregisterNotificationCallback(callbackID)` ‒ if passed the callback
ID returned from the previous method, removes the callback and
unsubscribes from relevant group, if there's no more callback for the
group. After this, the callback would not be called any more.
The callback would look like `callback(notificationName, params)`, as
passed to the `createNotification` from ticket #2930.
It should allow registering multiple callbacks for the same notification
group, so libraries that live inside the same program don't accidentally
fight over one if they both need the same notifications.
The proposal is to modify the `checkCommand` method to recognize
notifications and dispatch them similarly to how it calls commands.
--
Ticket URL: <http://bind10.isc.org/ticket/2931>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list