On 23/12/2018 18:16, Stefan Seelmann wrote:
On 12/23/18 4:34 PM, Emmanuel Lécharny wrote:
Touching base, soon. I'm done with all the standard operations, all the
controls (the 23 of them...), i'm almost done with the Intermediate
Response (SyncIInfoValue) and then I will have to process the
ExtendedOperations. This is easier and easier.
I'm talkingh about Decorator romovel here (the reverse encoding is fully
done). If I'm not to buys with external tasks (like in familly tasks
;-), I may be done tonite with extended operations.
Once completed, I have a couple of cleanup tasks to do - not really big
-, then there are a few things I'd like to do before cutting a release :
- make the Asn1Decoder completely stateless. Currently, we store a bit
of status in it, which deserves to be moved to the Container. This
should not take too long.
- then I want to make the Asn1Buffer allocated in a Thread Local
Storage, to avoid having to allocate it for every operation that
requires some encoding.
- I want to remove all the JNDI part of the API (but that may be
post-poned to the next release)
- last, not least, I think the Mutable/Immutable SchemaObject is a mess.
I'd like to rethink this part a bit. Same thing, might be for a next
release.
If you have anything you'd want to see in the coming release, please let
me know !
You mean a milestone release, right?
Correct.
Then all fine from my side, current
API and server master/snapshot work well with Studio.
I don't think the changes I'm currently doing are going to impact Studio.
For a final 2.0 API release I'd like to suggest changes in SSL/TLS
certificate handling, I'll write about that in a separate thread.
Sure. The SSL/TLS certificate support in the API is a bit defficient...
Waiting to read you :-)
