[Dar-libdar_api] Re: dar_manager API

[Johnathan B. <jk...@co...>]

Hi Denis,

Denis Corbin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Johnathan Burchill wrote:
> | Hi Denis,
> |
> 
> Hello Johnathan,
> 
> Sorry for the late reply, I have a ISP problem for now, and could only
> now find an old modem to have a temporary backup solution to connect to
> Internet. :-/

Too bad, but whatever works...

> 
> | I hope things are well with you.
> 
> yes, over this ISP problem, thanks. :-)
> 
> | I'm settled in the U.S. and now have some
> | time to think about dar/kdar.
> 
> Cool, I hope you realize how lucky you are!  :-)

I'm doing okay :).

> 
> | Glad to see you've made the move to have
> | dar_manager in the API. While it looks like you haven't made an official
> | announcement yet, I'll comment and ask questions anyway.
> 
> Yes, this is recent, the "Changelog" is always up to date. Your comments
> are welcome, as well as other's.
> 
> |
> | The API includes functions for manipulating the path to the dar binary.
> | Shouldn't the database object just call libdar functions directly
> through the
> | API?
> 
> Well, This must be considered. There might be some historical reasons
> that let to that situation (dar_manager appeared before libdar).
> 
> |
> | add_archive(...) requires a catalogue reference. It seems akward from a
> | developer point of view: macro_tools.hpp has to be included in order
> to use
> | the "macro_tools_get_catalogue_from()" helper to get the catalogue. This
> | could be called from within add_archive() directly, no?
> 
> Well, maybe I don't properly understand your remark, but, if this is
> called from within add_archive() directly, what would you give to
> add_archive(), a filename and path? right? So you cannot use an
> catalogue from memory. Suppose you make a backup and want to add it
> automatically to a dar_manager database. If using a filename, you will
> not be able to use the catalogue in memory but instead will have to load
> it from just written file...
> 

The point is that there is nothing in the API which lets me get access to a
catalogue. I expected add_archive to accept a pointer to an archive object,
or an archive object to have an accessor to its catalogue which can then be
passed to add_archive. The macro_tools_get_catalogue() function is not
actually part of the public API, and a given archive's cat member is
private.

Regards,
JB

> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
-- 
Johnathan K. Burchill, Ph.D.
jk...@co...