Preventing dup backend names with dynamic backends in VMODs

Dridi Boukelmoune dridi at
Mon Nov 16 12:23:09 CET 2015

On Mon, Nov 16, 2015 at 11:27 AM, Poul-Henning Kamp <phk at> wrote:
> --------
> 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.

Don't worry, I want to prepare my VCL temperature fixes first as we
discussed in Stockholm. I will remove the ABI breakage from when I
submitted it before 4.1, hopefully in time for the next VDD.

And I have a probably controversial solution I'd like to propose too :)


More information about the varnish-dev mailing list