BIND 10 #2225: Implement counters into Xfrout (3/3)

[BIND 10 Development]

#2225: Implement counters into Xfrout (3/3)
-------------------------------------+-------------------------------------
            Reporter:  naokikambe    |                        Owner:
                Type:  enhancement   |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  xfrout        |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20121204
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  7             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:21 naokikambe]:

 > Sorry, I couldn't understand exactly what singleton is as you mentioned.
 That is, is it not allowed to return an instance created before? If so, it
 isn't so difficult to revise to return a newly created instance, I think.

 In that we cannot have multiple xfrout counter objects, for example.
 Conceptually I don't see any difficulty in that, because counters are
 essentially a map from some ID to integers.  If the current singleton
 design is to simply allow cool syntax sugar like this:
 {{{#!python
   Counter.inc_xfrreqdone(zone_name)
 }}}
 I *personally* strongly oppose to the idea.

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