In message <[email protected]>, Nils Goroll writes:
>While it would be easy to implement VCL functions (preferrably in a module) for
>such digests always returning a STRING representation with some encoding
>(base64
>or whatever), for the VSLP director (which I briefly introduced here some time
>ago and which we will publish when an important rewrite is done), it would be
>really handy to also get an INT (or, more specifically, UINT32) representation
>for digests.
Compared to the any sensible digest algorithm, the string encoding is
totally nonvisible in the cpu-usage, so I am not convinced that it is
worth the hazzle of adding new datatypes to VRT.
I would simply write a vmod with digest functions somewhat like:
md5_hex(STRING_LIST input)
sha25_base64(STRING_LIST input)
and be done with it.
--
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]
http://lists.varnish-cache.org/mailman/listinfo/varnish-dev
