[Opendnssec-develop] UML package diagram

[Stephen.Morris at nominet.org.uk]

opendnssec-develop-bounces at lists.opendnssec.org wrote on 25/02/2009 
13:44:22:

> Rickard,
> 
> > Stephen, is that similar to what you had in mind?
> > 
> > http://www.opendnssec.se/wiki/Signer/Phase1/HowItWorks
> 
> This diagram brings a lot of clarity.  I cautiously checked it to 
conform
> to my ideas (which is what I think these diagrams are there for) and I 
see
> a full match.  Well done!
> 
> -Rick
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

It is very close to what I had in mind and I fully agree with Rick in that 
it brings a lot of clarity.


I would, however, suggest some minor changes:

* Change "KSM CLI" to KSM, remove "libksm", and have both "KSM" and "KASP 
Enforcer" communicate directly with the database.  The reasoning here is 
that KSM and the enforcer will exist as separate processes in the running 
system.  The fact that they use libksm is just a detail of their 
implementation.

* Change "Signer Engine CLI" to something like "SECP" (Signer Engine 
Control Program - sorry, it's the best I could come up with at short 
notice).

I suggest removing "CLI" from "KSM CLI" and "Signer Engine CLI" again 
because the CLI is just an implementation detail.


Stephen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20090226/8f3427ff/attachment.htm>