-------- In message <CABoVN9DEjdVU1XL1QWwn8DycHSfcVoLdRB-z=h5jueepy4m...@mail.gmail.com>, Dridi Boukelmoune writes: >> But I am also seriously wondering if we should go even further and >> have varnishd *only* produce JSON output, and leave the render-for-humans >> aspect to varnishapi or even varnishadm. > >Ideally implement it in libvarnish.a and expose it in libvarnishapi, >with a way for varnishadm to specify a window size in interactive >mode. This way varnishd -d will be able to produce the plain text >output.
I think you need to unpack that a bit before I follow ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
