BIND 10 #1914: CC library should allow asynchronous waits on messages
BIND 10 Development
do-not-reply at isc.org
Thu May 17 19:27:43 UTC 2012
#1914: CC library should allow asynchronous waits on messages
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
vorner | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120529
medium | Resolution:
Component: msgq | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: N/A | Estimated Difficulty: 8
Feature Depending on Ticket: msgq- | Total Hours: 0
ng |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
The branch is ready for review. It is probably slightly larger than usual,
but most of the diff should be comments, documentation and tests. The
actual amount of active code is relatively small.
There's one controversial thing. I put the functionality to
`ModuleCCSession`. This is because it was easier to put it there than to
the `isc::cc::Session`. It might be better from the interface point of
view to be there, but as we don't want to spend too much time on msgq
stuff now and the two are strangely intermixed and badly designed anyway
and we may want to refactor them sometime in future, I think it is not a
big deal.
The goal is to allow two things in future:
* Asynchronous RPC calls (eg. call something and not wait for the answer,
just handle it when it comes).
* Receiving notifications.
Once we need some of this, I think we will want to do some wrappers around
this, which will save time in long term and will not be much more work in
short term either.
--
Ticket URL: <http://bind10.isc.org/ticket/1914#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list