I did som cleanup in the varnishapi library this morning, and I want
the VMOD writers to pay a bit of attention.
VUT, VTIM, VSB, VAS and VCS are now partially exposed by libvarnishapi.
I have not exposed everything in them (yet), only the bits needed to
compile the tools in the tree (varnishlog/ncsa/...)
Should we expose all of these function sets ?
Should we also expose VPF, VSS, VSA, VTCP ?
I may also rename the SHA256 to VSHA256 in order to stick strictly
to the V* namespace...
Input, comments...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@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@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
the VMOD writers to pay a bit of attention.
VUT, VTIM, VSB, VAS and VCS are now partially exposed by libvarnishapi.
I have not exposed everything in them (yet), only the bits needed to
compile the tools in the tree (varnishlog/ncsa/...)
Should we expose all of these function sets ?
Should we also expose VPF, VSS, VSA, VTCP ?
I may also rename the SHA256 to VSHA256 in order to stick strictly
to the V* namespace...
Input, comments...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@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@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev