Karl, > > there was never a generic patch with a sensible interface. If you > > are interested in the second axis thing, please, before you start > > coding, come up with a configuration method and discuss it on the > > developers list ... > > I'll have to think more about this ... > The grid will probably be the most difficult problem to solve.
exactly where I always end up when I start thinking about it :-) > > what is it that you try to achieve ? with integers for data storage ? > So my wishlist would be: > * add the ability to store any common data value (8,16,32,64bit int > and single/double floats) - to use the best match for the purpose. > > I fully understand that this doesn't strike you as a very rewarding > venture - I'm just thinking about the feasability to do it myself. hmmm ok ... I guess the fundamental problem we are striking here, is the 'get back exactly what I put in' bit. This is contrary to rrdtools philosophy of enabeling you do put in data when ever you manage to sample it, and then adjusting for the time jitter. This does not work with integers ... now, floats vs doubles, this might be another matter, but integers will just cause so much trouble since the results will be different from what people expect them to be, that I fear an explosion of unhappy users who managed to totally mess up their data by storing it as integers ... cheers tobi > > Many thanks. > > cheers > > - Karl > > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902 _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
