2000-06-21 23:50:43 +00:00
|
|
|
Copyright (C) 1999, 2000 Internet Software Consortium.
|
|
|
|
|
See COPYRIGHT in the source root or http://www.isc.org/copyright for terms.
|
1999-03-11 00:45:31 +00:00
|
|
|
|
2000-06-22 22:00:42 +00:00
|
|
|
$Id: rdataset,v 1.3 2000/06/22 21:53:56 tale Exp $
|
|
|
|
|
|
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
|
