On Mon, Nov 16, 2015 at 11:27 AM, Poul-Henning Kamp <[email protected]> wrote: > -------- > In message > <cabovn9avhev3pb_90hrgckdtdnhu0c83chdesvfbw6abc5g...@mail.gmail.com> > , 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() >>> $backend.name() >>> >>> 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 :) Dridi _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
