2018-03-15 18:32:45 -07:00
|
|
|
Copyright (C) Internet Systems Consortium, Inc. ("ISC")
|
2016-06-27 14:56:38 +10:00
|
|
|
|
2018-03-15 18:32:45 -07:00
|
|
|
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
|
2018-02-23 09:53:12 +01:00
|
|
|
|
2004-03-05 05:14:21 +00:00
|
|
|
$Id: rdataset,v 1.6 2004/03/05 05:04:46 marka Exp $
|
2000-06-22 22:00:42 +00:00
|
|
|
|
1999-03-11 00:45:31 +00:00
|
|
|
Need way to "dup" an rdataset (i.e. different rdataset handle, same underlying
|
|
|
|
|
data).
|
|
|
|
|
|
|
|
|
|
DB addnode routine should take an rdataset *, which, if non-NULL, would be
|
|
|
|
|
attached to the added rdataset.
|
|
|
|
|
|
|
|
|
|
Need credibility, security status.
|
|
|
|
|
|
|
|
|
|
Cache security status in rdataset. Have rdataset supply methods to get/set
|
|
|
|
|
the security status. For RBTDB, it goes something like this:
|
|
|
|
|
|
|
|
|
|
get:
|
|
|
|
|
if (cached status == pending)
|
|
|
|
|
lock node lock
|
|
|
|
|
read rdataset's status
|
|
|
|
|
unlock node lock
|
|
|
|
|
update cached status
|
|
|
|
|
return (cached status)
|
|
|
|
|
|
|
|
|
|
set:
|
|
|
|
|
require that status cannot go backwards (e.g. OK to pending)
|
|
|
|
|
lock node lock
|
|
|
|
|
write rdataset's status
|
|
|
|
|
unlock node lock
|
|
|
|
|
update cached status
|
