>
> I'm thinking more in terms of a CTX parameter passed to a different API.
> The problem with many caching ideas and the current ASN1 library is that
> things could be modified and the cache have no way of determining that
> it is now invalid. Some parts are modified using a structured API
> whereas others by directly accessing structures.
Right, if one assumes that one can create structures i2d them, and then
add/remove parts of them, i2d them, etc, then all this may get
difficult.
>
> Oh believe me it is bad. The deeper you look into it the worse it
> gets...
Ok, I propose historically grown and fortunately not functionally stabilized. :-)
>
> > If one decides the object structure, it might be useful to add a flag to
> > whether the data should be freed when free is called, this would also
> > avoid copying larger string buffers in some cases, especially
> > when they could be static somewhere.
> >
>
> Yes something like that exists with ASN1_OBJECT. It could be added to
> ASN1_STRING as well.
As much elements as possible.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
