[PATCH] add documentation about backend naming for VMOD authors

Poul-Henning Kamp phk at phk.freebsd.dk
Mon Nov 2 09:52:28 CET 2015

In message <CABoVN9DVoRbvHdOrYAM8WpKbfowoMfXQb5eGSEFfW_Ho=Gn9Kw at mail.gmail.com>, Dridi Bouke
lmoune writes:
>Sorry for the frenchism but it's turning into a "dialogue de sourd" :(
>> VCC is not involved in dynamic backends.
>I *know* that.
>In the "Writing a director" documentation I *recommend* directors
>writers to back their director with a *VMOD object* 
>Crossing fingers that this time I'm making some sense.

Not really.

VMOD objects are only usable if you know the number of such backends
at the time you write your VCL code.

What about VMODs that create an unknown number of backends ?

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 mailing list