Another general ASN1 question.
The revised OpenSSL ASN1 code will eventually have support for I/O based
operations in addition to the current memory based operations which need
to have the entire structure in memory (tricky if its a 1Gb structure on
tape).
Doing blocking I/O is fairly straight forward.
Handling non blocking I/O is quite a bit harder because the ASN1 decoder
or encoder must be able to save its internal state and restart where it
left off.
So the question: how many people would want non blocking I/O support? If
no one or hardly anyone wants or needs it then there isn't a lot of
point. However if there's considerably demand it would be worth looking
into.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
