-
Key: PKI-18
-
Legacy Issue Number: 4444
-
Status: closed
-
Source: Fujitsu ( Stephen McConnell [X] (Inactive))
-
Summary:
After going through the PKI Repository module in more detail I'm running
into a number of problems concerning implied implementation approach that is
forced on the developer (effectively the implied implementation is an LDAP
directory). It seems that the Repository is defined with the assumption
that (a) storage slot attribute names are passed as parameters and (b) the
storage values for attributes are always an any. This complicates the
implementation approach if you have alternative "more structured" storage
systems available (e.g. PSS - for example, using PSS I can store CORBA
values and object references directly with complete type safety and
practically zero additional code.This "implementation constraint" is a supposedly "implementation
independent" spec is a significant issue. -
Reported: PKI 1.0b1 — Thu, 2 Aug 2001 04:00 GMT
-
Disposition: Resolved — PKI 1.0
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT