VCL storage discussion summary

[Federico Schwindt]

What about something like this:

- NULL or "no setting" means default storage (this is the same as no
backend).
- default means the first non-Transient storage for cache insertions,
Transient for anything else (pass and request bodies).
- No more RR on storages by default. If this is wanted, it should be set
explicitly somehow (VMOD?)

If we failed to allocate using the selected storage we fallback to
Transient, always.
If Transient fails because it's capped and we couldn't make space, we fail
hard.

Comments?

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

> --------
> In message <CAJV_h0b-XvA9Skc646fkW5nEJg4MjzbG1kuXG3
> RTqa686AkS4g at mail.gmail.com>
> , Federico Schwindt writes:
>
> >This might be obvious but are we considering NULL a "no setting" as well
> or
> >only when a VMOD returns NULL?
> >
> >If it's the latter I agree. The former would be a breaking change.
>
> Well, that's why I'm asking:
>
> If vmod returns NULL does it mean
>
> A) Failure to select stevedore
>
> B) Use default stevedore selection
>
> ?
>
> --
> 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/c2cbc086/attachment.html>