VCL storage discussion summary

[Federico Schwindt]

Assuming this will depend on whether this is the client or the backend side
(request vs response), yes,
for the request body Transient being the default makes sense (current
behaviour).




On Mon, Oct 10, 2016 at 5:55 PM, Poul-Henning Kamp <phk at phk.freebsd.dk>
wrote:

> --------
> In message <CAJV_h0Yx8t4MoLpfk3kRpukxuyotXHesf4
> ctATgu2QwFTqvxxA at mail.gmail.com>
> , Federico Schwindt writes:
>
> >If setting or using a storage cannot fail I'd say kill _hint (eventually)
> >and just use storage.
> >
> >If there is a chance of failing, I'd keep the _hint. I'd avoid having
> both.
> >Having backend_hint and backend is confusing enough already.
>
> I agree, and I'd like to kill backend_hint as well.
>
> That said, in both cases we need to deal with "no setting" and "vmod
> returning NULL".
>
> For backend, it's the default backend.
>
> Is it Transient for storage ?
>
> If so, I think we have a decision...
>
>
> --
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20161010/1a7f7ec2/attachment.html>