b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob HalleyNeed way to "dup" an rdataset (i.e. different rdataset handle, same underlying

b22332fc28297c3851d8dd118af08a693339d56bBob Halleydata).

b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob HalleyDB addnode routine should take an rdataset *, which, if non-NULL, would be

b22332fc28297c3851d8dd118af08a693339d56bBob Halleyattached to the added rdataset.

b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob HalleyNeed credibility, security status.

b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob HalleyCache security status in rdataset. Have rdataset supply methods to get/set

b22332fc28297c3851d8dd118af08a693339d56bBob Halleythe security status. For RBTDB, it goes something like this:

b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob Halley get:

b22332fc28297c3851d8dd118af08a693339d56bBob Halley if (cached status == pending)

b22332fc28297c3851d8dd118af08a693339d56bBob Halley lock node lock

b22332fc28297c3851d8dd118af08a693339d56bBob Halley read rdataset's status

b22332fc28297c3851d8dd118af08a693339d56bBob Halley unlock node lock

b22332fc28297c3851d8dd118af08a693339d56bBob Halley update cached status

b22332fc28297c3851d8dd118af08a693339d56bBob Halley return (cached status)

b22332fc28297c3851d8dd118af08a693339d56bBob Halley

b22332fc28297c3851d8dd118af08a693339d56bBob Halley set:

b22332fc28297c3851d8dd118af08a693339d56bBob Halley require that status cannot go backwards (e.g. OK to pending)

b22332fc28297c3851d8dd118af08a693339d56bBob Halley lock node lock

b22332fc28297c3851d8dd118af08a693339d56bBob Halley write rdataset's status

b22332fc28297c3851d8dd118af08a693339d56bBob Halley unlock node lock

b22332fc28297c3851d8dd118af08a693339d56bBob Halley update cached status