[EMAIL PROTECTED] wrote:
Where: U=Updated data exchcnage state
P=Pending data exchange state
C=Commited data exchange state
Sender: U and C Receiver: P and C
Are these all the required data exchange states ? I know Michael talked about a rejected state, but I am not sure I understand that one.
Receiver: RIf a CA receives an APPROVED CSR but the actual state of the CSR is DELETED or ARCHIVED then the object will be rejected. If we don't signal this reject then the sender will send the object forever. If we send a normal commit then this is more than unfair because the client writes a commit into it's protocol instead of erasing it.
If we do go for another table, on the CA there would be (("number of
objects" x "number of nodes") + "number of global objects") records and on
each node there would be "number of node objects" + "number of global
objects" records.
Perhaps we should split the discussion into a state part where we define the minimal state management requirements and a SQL part where we define the database handling. I think first we should identify a minimalistic but 100 percent safe protocol and then we can think about the implementation.
I try to identify all possible situation until tomorrow and then I think a small chat is a good idea.
Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
