I'm working on a prototype integrating the signature-api with the config stuff & the spec api. Couple of things:
#1 I'd like to propose a relatively minor cosmetic change: s/SignatureMethodAlgorithm/SignatureMethod/ and, s/getAlgorithmMethod/getAlgorithm/ ... slightly less of a mouthful this way. I'll commit it tomorrow unless anyone objects. #2 I'm trying to understand whether it would be possible for the SignatureMethodAlgorithm interface to be refactored to just use the Key interface, or (SigningKey, VerifyingKey) directly. I assume it's defined like this so an implementation can require it's own key classes to be used? The problem is that I don't think we will be able to use the ServiceLoader mechanism to discover and use signature implementations. In fact it will be hard to use any form of interface which uses generics in this way. I had anticipated being able to perform a lookup, like so: SignatureMethodAlgorithm getSignatureMethod(String algorithm); Thoughts/comments? p
signature.asc
Description: OpenPGP digital signature
