Markus Raab wrote:
> 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
>
Please elaborate a bit more on this
> * API rework
> - mark functions to be necessary for bindings
> - mark obsolete functions
> - improve documentation
>
most needed!
> - writing test functions
> - mark c-helper functions
> * make kdbHandle binary compatible
>
This might not be needed... but a stable (and future-proof, and secure,
and efficient) API is a MUST right now.
The threads on Elektra architecture should be reviewed, a design needs
to be completed and then we can go on implementing every remaining bit.
> * ini backend
> * cpp bindings
> * python bindings
> * scheme binding
> * (with example apps to bindings)
>
Ok. I would suggest C++ and Python to be the highest priorities, Perl
and Scheme can come later.
> additional (if we have time or it is needed):
> * notification system + scheme binding
>
The notification system (probably inspired on FAM API) is badly needed
if we want applications to be responsive to changes without a complete
restart / config reload.
> * benchmark for large keysets
> * debian packages (one is debian maintainer)
>
I will help on this ;)
> Questions:
> Do you have other ideas to have elektra improved?
> (coding work only)
>
Complete the design first: elektra daemon, backend "layering"/mounting,
security considerations and the like are all to be taken into account.
> Shall we fork elektra or directly work on svn?
>
I suggest a branch in the SVN repos.
> 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)
>
Please devote enough time to planning and coordinate with "upstream"
proper [upstream being mostly Avi, Yannick and you, I presume].
Otherwise we would only be wasting everybody's time.
Unfortunately, I can't promise that I will be devoting a lot of time to
this, but I think I can help quite a bit with the specification/design
phase.
Good luck with your course, Markus.
Cheers,
J.L.
-------------------------------------------------------------------------
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
