BIND 10 #192: Data source hotspot cache

[BIND 10 Development]

#192: Data source hotspot cache
-------------------------+--------------------------------------------------
 Reporter:  each         |        Owner:  each                                          
     Type:  enhancement  |       Status:  reviewing                                     
 Priority:  major        |    Milestone:  05. 3rd Incremental Release: Serious Secondary
Component:  b10-auth     |   Resolution:                                                
 Keywords:               |    Sensitive:  0                                             
-------------------------+--------------------------------------------------

Comment(by each):

 Replying to [comment:8 each]:

 Oops, a bunch of text got cut out by mistake.

 > > One practical reason for this is that we may actually want to have
 multiple different caches if/when we support views.
 >
 > Perhaps, but then we'll be wanting to

 Then we'll be wanting to declare a cache for each view which every query
 reaching that view would use... and it seems to me to this presents much
 the same set of problems as a global variable (or nonlocal static member)
 when it comes to thread safety and such.

 In the current case, when we don't have a need for multiple caches--and in
 fact we explicitly prefer that the server only use one--using a nonlocal
 static member means we can instantiate a Query and it Just Works--there's
 no need for the caller to explicitly set up a cache in advance.  b10-auth
 doesn't need to know there's any such thing as a HotCache.

 I have no particular objection to doing it the way you suggested, but I do
 think there's some advantage to code that does the right thing without
 being told.

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