libelektra is probable to be continued as a university project at TU Vienna during the software engineering 2 lecture [0].
Current we are 3 People trying to continue the project relating: * ability to mount backends * API rework - mark functions to be necessary for bindings - mark obsolete functions - improve documentation - writing test functions - mark c-helper functions * make kdbHandle binary compatible * ini backend * cpp bindings * python bindings * scheme binding * (with example apps to bindings) additional (if we have time or it is needed): * notification system + scheme binding * benchmark for large keysets * debian packages (one is debian maintainer) Questions: Do you have other ideas to have elektra improved? (coding work only) Shall we fork elektra or directly work on svn? We can't find broad conventions, that means we three will decide how to do it, and what to do. After the work it is of course possible to patch out things which can be done in a better way or are too incompatible. On the other hand its also possible to get the patches into the main branch. (This might be so complicated that it will not be done, e.g. if there is a api change in fork, I can't make the scheme binding work for pre-api changed elektra) thank you Markus Raab [0] (in german) http://se-linux.inso.tuwien.ac.at/tw/Se2 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Registry-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/registry-list
