[PATCH] add documentation about backend naming for VMOD authors
phk at phk.freebsd.dk
Mon Nov 2 09:20:36 CET 2015
In message <CABoVN9DKpKip1gh5cavrAx4GRT7vyMMM=CyWAs8SNUhON4_mhw at mail.gmail.com>, Dridi Bouke
>>>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
>> backends ?
>We can't have two VMOD objects from different VMODs (or even from the
>same VMOD) having the same vcl_name for a given VCL. That's a
>guarantee we get from libvcc.
VCC is not involved in dynamic backends.
As Geoff said, a VMOD can spit out as many backends as it wants...
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