--------
In message
<cabovn9a-wkfejm9jabfy+fojg8zsfa+y+v-ursk2xjddq05...@mail.gmail.com>, Dridi
Boukelmoune writes:
>libvarnishapi has a clear scope,
Yes, that's for VSM/CLI only applications.
>but libvarnish OTOH is a catch-all library kind of like libc
>and contains things that are sometimes completely unrelated.
It is our internal library.
But if you look carefully, you'll see that we drag a lot
libvarnish into libvarnishapi already:
../libvarnish/vas.c \
../libvarnish/vav.c \
../libvarnish/version.c \
../libvarnish/cli_common.c \
../libvarnish/cli_auth.c \
../libvarnish/vin.c \
../libvarnish/vmb.c \
../libvarnish/vre.c \
../libvarnish/vsb.c \
../libvarnish/vtim.c \
../libvarnish/vnum.c \
../libvarnish/vsha256.c \
So in practice the libraries are less different than you'd think...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[email protected] | 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
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
