Live data from Hacker News

Vinyl Cache and Varnish Cache

vinyl-cache.org

41–45 of 45 posts

Re: Vinyl Cache and Varnish Cache

#41
This was published in April, and we are far from consensus on what is “varnish”. Lots of distributions are now packaging vinyl and calling it varnish, some are pointing to the varnish repo instead (Fedora, Homebrew).

I’d left a comment last time, but haven’t tracked it since: https://news.ycombinator.com/item?id=47728216

Re: Vinyl Cache and Varnish Cache

#43
I bet they're sorry now for sticking to principles, no one forced them to change the name. As it looks now, they'll be developing upstream but "everyone" will be using fork. Explain to me how to use vmod-tcp pacing with haproxy handling tls? Not to mention mess this caused with vmods.

Re: Vinyl Cache and Varnish Cache

#45
post #40

Earlier quoted context omitted.

I am talking pre mariadb times.

Are you maybe confusing “downstream” with “mainstream”? Being “downstream” of a product means that you are a derivative of that product (your upstream), taking in basically all of their code and adding your own on top.

So the meaning of downstream is different for SuperSQL (the direct derivative) and TodoApp (the commercial product)?

Imho, downstream are all consumers/users of that product. I guess it's arguable how a package manager positions in that terminology.

Edit: Also I originally said, "it was the thing used downstream", which just is to describe the consumers. Also not sure what I got into, because the original question is wildly confusing!

Post reply on HN