[master] 11d55148a Put some serious red tape on VCL_STRANDS

Nils Goroll nils.goroll at uplex.de
Thu Nov 21 11:05:19 UTC 2019


On 19/11/2019 19:07, Dridi Boukelmoune wrote:
>>     This also begs the following question: can it ever be safe to let a VMOD
>>     function return a STRANDS? Maybe it should be banned from return types.
> 
> I think the rules I laid out makes this fine in the scope of a single
> VCL statement.

My understanding is that we should apply the same rule as for any other data
types in VCL: Ensure that they have at least TASK lifetime.

Then, the rules for keeping references to STRANDS become the same as for BLOBs:
If you want to keep a reference for longer than a TASK, you need to make a copy.

For that copy, I would think that the STRANDS should be collapsed and we might
want to add some convenience utilities.


-- 

** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

tel +49 40 28805731
mob +49 170 2723133
fax +49 40 42949753

xmpp://slink@jabber.int.uplex.de/

http://uplex.de/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-commit/attachments/20191121/76362ad4/attachment.bin>


More information about the varnish-commit mailing list