You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Jiajia Li (JIRA)" <ji...@apache.org> on 2015/08/04 07:31:04 UTC
[jira] [Updated] (DIRKRB-159) Having a decoartor for each type
(like BER/CER/DER) of encoding
[ https://issues.apache.org/jira/browse/DIRKRB-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiajia Li updated DIRKRB-159:
-----------------------------
Fix Version/s: 1.0.0-RC2
> Having a decoartor for each type (like BER/CER/DER) of encoding
> ---------------------------------------------------------------
>
> Key: DIRKRB-159
> URL: https://issues.apache.org/jira/browse/DIRKRB-159
> Project: Directory Kerberos
> Issue Type: Improvement
> Reporter: Kai Zheng
> Fix For: 1.0.0-RC2
>
>
> Below is from [~elecharny]'s email, giving the thoughts:
> {noformat}
> we do the encoding/decoding in the ASN1 type instances.
> That's ok, but as soon as we have to deal with various type of encoding
> (BER/CER...) this cipple the code with if/else/then.
> What about having a decoartor for each type of encoding ?
> {noformat}
> Below is [~drankye]'s response in email:
> {noformat}
> I agree. If we're going to support BER and DER both well or new schemes,
> then we need such. It won't introduce API change for the types and is only
> for internal encoding/decoding implementation, right ?
> Could you have a simple illustration or example,
> say how to do that for the simple Asn1Boolean type ? Thanks.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)