On Mon, Jun 09, 2008 at 03:04:25PM +0200, Sebastian Harl wrote: >> > The applet should basically do this instead: >> > 0) [APP] option handling >> > 1) call rrd_open() >> > 2) [APP] eventually inspect the header. >> > 3) [APP] setup desired start, end, step. >> > 4) call rrd_find_rra() or rrd_find_best_rra() /* or however it would be >> > called */ >> > 5) [APP] adjust start, end, step to legit values. >> > 6) call rrd_fetch_fn() >> > 7) [APP] rrd_close(); rrd_free() >> > 8) [APP] do something with the results and exit. > >Sounds good to me. In addition, it might make sense to add the >additional features implemented in rrd_reader to rrd_fetch. What do you >think?
A rrd_find_rra and rrd_find_best_rra already exist in librrd, but should be factored out as separate functions, so yes, i agree. Not sure about which additional features of rrd_reader you're thinking? I don't have time ATM so please feel free to take any and all parts of it that you like or think could be useful :) cheers, Bernhard _______________________________________________ rrd-developers mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
