Hi, It seems to me that the graph portion of rrdtool is turning into a front-end type of program rather than a backend program. This is not a bad thing however now may be the time to rethink about this. The grapher portion becomes quite large.
Just as a proposal for discussion: what if we take the DEF,CDEF and VDEF stuff apart. This generates arrays of numbers and can change the databases (Jake's stuff). Processing the arrays is IMHO a task for a front-end application which could be called rrdgraph. The same arrays could be fetched by another front-end application called rrdreport. Of course, the current "rrdtool graph" will not have to go per se. It can be made a hook to the front-end if desired. It may be enough to modify rrdtool fetch slightly and in the new rrdgraph front-end application we'd make DEF a hook to fetch. Consolidating the arrays into something suitable for graphing is already a job for the front-end part. What do you all think about this? cheers, -- __________________________________________________________________ / [EMAIL PROTECTED] [EMAIL PROTECTED] \ | work private | | My employer is capable of speaking therefore I speak only for myself | +----------------------------------------------------------------------+ | Technical questions sent directly to me will be nuked. Use the list. | +----------------------------------------------------------------------+ | http://faq.mrtg.org/ | | http://rrdtool.eu.org --> tutorial | +----------------------------------------------------------------------+ -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-developers WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
