In message
, Dridi
Boukelmoune writes:
>I think the confusion is mostly that we make an amalgam of the VMOD
>object and the underlying director. [...]
Well, there is a lot of ways to get confused, and I have yet to find
any obvious ways to make all the confusion go away.
I already
On Wed, Sep 19, 2018 at 12:19 PM Nils Goroll wrote:
>
> my example was missing the point
>
> On 19/09/2018 12:14, Nils Goroll wrote:
> > backend "b" which you now want to layer under director "d": all instances
> > of "b"
> > in the vcl now need to be replaced with something like "d.backend()".
my example was missing the point
On 19/09/2018 12:14, Nils Goroll wrote:
> backend "b" which you now want to layer under director "d": all instances of
> "b"
> in the vcl now need to be replaced with something like "d.backend()".
... while, if we had a common accessor, b could be renamed to bb
backends and directors are both represented as VCL_BACKEND aka struct director,
yet VCL authors need to differentiate between them:
* backends are represented directly as the BACKEND type
* directors are represented as vmod objects, for which a method (.backend() by
convention only) returns a
