> One of the things I wrote into the XML Encryption code was an "Algorithm > Handler". It *can* still use the encryption constants, but it will also > work if you pass in a URI to the (for example) > XENCCipher::encryptElement() method. The AlgorithmHandler class is > empty by default, and at initialisation has a number of algorithms > registered.
Yeah, I saw it. And got briefly excited until I figured out it only worked for encryption. ;-) > So one of the things I already wanted to do for 1.3 was refactor the > signature processing code to insert the same AlgorithmHandler in a > manner that is extensible in the same fashion. I think that would solve > the problem you mention below, but by using the methodology above we > should be able to avoid breaking the current API. Agreed. I just wanted to bring it to your attention. I'm on the verge of a major release that may need to last a while, so I'll probably slap in a temporary mapping file people can extend to let me use the URIs exclusively and map them at runtime to enum numbers to pass into or from the library. Thanks, -- Scott
