BIND 10 #2853: Python wrapper of data source extensions

[BIND 10 Development]

#2853: Python wrapper of data source extensions
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  muks
                Type:  task          |                       Status:
            Priority:  medium        |  reviewing
           Component:  data source   |                    Milestone:
            Keywords:                |  Sprint-20130625
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  5             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => muks


Comment:

 Hello

 I seem to be getting confused around too many responses to too many
 things. What is the motivation for splitting the constructor? Is it
 something outside of this ticket? Or reaction to some of the comments
 here?

 With the documentation, well, there must be some point where the C++
 object is taken and wrapped into python. And, in this point, it must be
 created by some C++ code that is wrapped into a python function/method.
 The parameter must be passed to the created object _somewhere_ and as the
 calling application is python one, it must be some python wrapper that
 calls the C++ routines to create it.

 So, which point in the wrappers is it? Is it one point or many? Is the
 value of the parameter hardcoded in the python wrappers, or can it be
 specified by some parameter of python wrapper somewhere?

 It is not possible to the object to come to existence out of thin air.

 With the code Jinmei deems unsafe, I think it is OK to know it never
 throws. But it should be marked there as a comment, because it's not
 obvious.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2853#comment:27>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development