[rrd-developers] RRDCacheD - Client rewriting path

[kevin brintnall]

> Hrm, I'm not sure that I agree with that. Why does the client's current
> working directory matter at all to the server? Think about other ways of
> remote access to files - all of them use some kind of base directory
> that's used whenever relative path names are specified: scp uses $HOME,
> Apache uses the document root, git-daemon supports a base path, etc. So,
> I think that by following the principle of least surprise RRDcacheD
> should behave like that as well. Let people think about $HOST:1.rrd
> instead of 1.rrd (where $HOST might be remote or local) - we're
> referring to a file on some $HOST after all ???

The existing code allows the daemon to work with any existing client
work-flow without requiring them to change their code.  That is important.

-- 
 kevin brintnall =~ /kbrint at rufus.net/