BIND 10 #2088: introduce MemorySegment class

[BIND 10 Development]

#2088: introduce MemorySegment class
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120717
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  scalable inmemory                  |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:19 muks]:

 > You and I understand what each other is saying at least. I think both
 approaches are equivalent in practice. You think checking is superior as
 the process gracefully exits at top-level and reports an allocation
 problem. Let's agree to disagree on this. :) The code now throws, which
 I'm fine with too.

 Okay...I'm feeling a bit guilty if you were not convinced but changed
 the code, but if you can live with that let's move forward with it for
 now.  I'd leave the ticket to you and Jelte at this point.

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