BIND 10 #2205: introduce a "data source configurator" thread in auth
BIND 10 Development
do-not-reply at isc.org
Wed Aug 22 17:56:33 UTC 2012
#2205: introduce a "data source configurator" thread in auth
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: task | Milestone: Next-Sprint-
Priority: | Proposed
medium | Resolution:
Component: | Sensitive: 0
b10-auth | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
background zone loading |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:2 vorner]:
> Maybe it's a bit of haskellism on my side, but whenever I do something
like this, the easiest (and most generic) approach is creating a work
thread with a queue of functions (or functors) ‒ something like a wrapper
around a thread, conditional variable and `vector<boost::function<void()>
>`.
>
> It is simple, generic and the code that needs to be backgrounded (like
the loading we plan) doesn't have to be split across multiple places ‒ the
code that needs something done in the background contains the functor as
well.
I'm not sure if I fully understand above. Can you provide some
sample code snippet to illustrate the idea more specifically?
In any case, specific ways to implement it is up to the developer
(and the reviewer, and if it's controversial on review we can discuss
it project wide). The approach mentioned in the description is just
an example to give a better idea of what should be done, and doesn't
have to be adopted literally.
--
Ticket URL: <http://bind10.isc.org/ticket/2205#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list