That's right. We have to choose a broadly supported backend and include all the supported binary packages. Basically, we could have the current Mavibot or JDBM as the fallback. We should really really get it work in the best on the most typical platforms, such as Linux, and wouldn't worry too much about the else.
Regards, Kai -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Monday, June 27, 2016 7:03 PM To: Apache Directory Developers List <[email protected]> Subject: Re: Rethinking Mavibot... Le 27/06/16 à 12:49, Zheng, Kai a écrit : > Thanks so much for the full explanation, Emmanuel. Sorry for my asking again. > >>> Otherwise, we could use LMDB, with a JNI wrapper. That is an option. But I >>> have no idea what it would cost us in term of packaging. > The packaging isn't really so much a problem. There is a nice way handling > this: the binary package could be put into the jar just as a resource and > while starting up it can be dynamically extracted, putted into a runtime > folder to be loaded. Many Java projects do this way. Yes, but that would require a built package for all the targets.
