Preventing dup backend names with dynamic backends in VMODs

Poul-Henning Kamp phk at
Mon Nov 16 11:27:11 CET 2015

In message <CABoVN9AVhev3pb_90hRgckdTdnhu0C83cHDesVfBw6abC5gxmg at>
, Dridi Boukelmoune writes:

>> The real fix would be to allow standardized (ie: builtin) methods on the
>> VCL_* types themselves, so that one could do things like
>>         $backend.ip()
>>         $
>> Implementing it will take some VCC hacking
>If needed I can take this one once I get enough bandwidth and more
>precise requirements, I'm getting used to dealing with VCC and
>backends :)

Please hold off until we have a design for the entire
VMOD_PRIV/VMOD_OBJ/Backend thing.  I want a clean future-proof solution
rather than more hacks.

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