|
|
| Q |
I have my own ASN.1 syntax. Can I use OneDecoder? |
| A |
Yes. One of the primary design requirements for OneDecoder was the ability to
reconfigure it to work with any custom ASN.1 syntax.
|
| Q |
Which encoding rules does the application support? |
| A |
OneBuilder supports BER, CER, DER, PER, UPER, XER,
and CXER encoding.
|
| Q |
How does OneDecoder cope with multiple ASN.1
syntaxes? |
| A |
OneDecoder extracts ASN.1 syntax information from specially prepared
configuration files. Each syntax is defined in one file and the files are
stored in a particular location. OneDecoder reads the contents of these files
at run time. To support a new syntax, a new configuration file needs to be
prepared.
|
| Q |
OneDecoder is very close to what I need but it does
not exactly meet my requirements. How can this be dealt with? |
| A |
OneDecoder is an evolving application. New features are being planned. Your
input can influence its future capabilities and direction. Depending on the
impact and size of your requirements it may be possible for Red Packet
Technologies to modify OneBuilder to suite your specific needs. For more
information contact Red Packet Technologies.
|
| Q |
How do I get more information about OneDecoder? |
| A |
Send your request indicating your name, company, and application to
info@redpackettech.com.
|
