V4 VCL roadmappery...

[Dridi Boukelmoune]

vcl_request
vcl_bereq
vcl_forward
vcl_transmit

I agree this is not easy to find a meaningful name, those might be
confusing :(

Best Regards,
Dridi

On Wed, Mar 20, 2013 at 1:56 PM, Poul-Henning Kamp <phk at phk.freebsd.dk>wrote:

> In message <
> CABUevEw2P64dcayQ2_rH_ZR-_sX7YcG95qb7q2wQJ4o_hNHyCg at mail.gmail.com>,
> Magnus Hagander writes:
>
> >> vcl_fetch{} becomes vcl_reponse{}
> >>
> >> A new vcl_fetch{}
> >>
>
> >Maybe I'm coming in late to this game, but is it really necessary to
> >reuse the old name? I'm seeing a lot of confusion amongst people for
> >the simple reuse of "purge" in version 3 to mean something completely
> >different to what it used to mean. This sounds like it could be even
> >worse... Probably a lot less confusing if a completely new name can be
> >invented, if it's a new function that does something else...
>
> Suggest a better name ?
>
> --
> 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.
>
> _______________________________________________
> varnish-dev mailing list
> varnish-dev at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20130320/7fd3d692/attachment.html>