[PATCH] add documentation about backend naming for VMOD authors
phk at phk.freebsd.dk
Mon Nov 2 08:52:11 CET 2015
In message <CABoVN9BWfXKWLKEp7fWpVvbHoqmA+h1_Q-BgOHccGqJ0Hbu-eg at mail.gmail.com>, Dridi Bouke
>> So what if two different VMODs both try to create a backend with the
>> same name ?
>If both VMODs rely on a vcl_name to name their backends (myvcl.mydir)
>then they can't get in this situation. That's my whole point.
And in a VCL which uses two different VMODs which create dynamic
>> In my view, the "magic behaviour" is to fail randomly for reasons the
>> VMOD writer has no control over...
>In case of a panic, you get a little clue: the VMOD file in the backtrace.
No matter what, I don't think this is panic material, unless the VMOD
writer feels that way about it.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the varnish-dev