Re: backend/director admin states

In message , Dridi Boukelmoune writes: >All we need is TheNewGuy(tm) to dump this on their desk :p Indeed, they grow up so fast, don't they ? :-) Anyway, I would like to get back to the actual underlying

Re: backend/director admin states

On Fri, May 4, 2018 at 9:42 AM, Poul-Henning Kamp wrote: > > The reason we have include/tbl/cli_cmds.h in the first place was > that I wanted some kind of "schema-light" for UX use, but that > didn't happen. Yes, that experiment failed, but I somehow succeeded in

Re: backend/director admin states

In message , Dridi Boukelmoune writes: >I experimented with this a while back and tried this: > >[...] > >I never completed the last experiment because the time I allocated >eventually ran out and I lost motivation to

Re: backend/director admin states

>>Maybe we should do that the other way around? Have all CLI commands >>reply with a JSON data structure, and CLI consumers like varnishadm, >>varnishtest or varnishd -d be able to output it in plain text (with >>this code centralized in libvarnish and exposed in libvarnishapi). > > I thought

Re: backend/director admin states

In message