[Dar-libdar_api] Re: problem compiling KDar with libdar CVS

[Denis C. <dar...@fr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Denis Corbin wrote:
| Hello Johnathan,
|
|[...]
|
| Things to review in the API are :
| - op_create & other functions must become methods of the archive class
| (for a more correct C++ design)

this has been done today (CVS). Still needs documentation.

| - what about thread cancelation ? Do we assume kdar will fork() rather
| than require a more complex mechanism to cancel a thread ?

If the thread cancelation does not implies any change, then we are very
near the definitive API specifications for version 3 so we could
"freeze" the API. Some last feature will only add a type in enumeration
(LZO compression, RSA encryption, etc.), but class, function or methods
definitions should not change at all.

My current actions are the following in order of priority:
- - documentation (review all in HTML format, API documentation first)
- - finish strong encryption (password from interactive question, or from
file, some few other strong encryptions algorithms)
- - LZO compression if time allows it (all development stop at end of
November for 2.2.0 pre-release phase)

|
| Cheers,
| Denis.
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBhoT9pC5CI8gYGlIRApa6AKCJAoCIASYsnjIon7/SolGXqbR9GgCeObOm
1b4v7uWQmtWL6ll7Y3m5PwE=
=FtiH
-----END PGP SIGNATURE-----