--------
In message <[email protected]>, Geoff Simmons writes:
>>>> A backend when popens a CGI command for this request ?
>>>
>>> I'm sure I wouldn't do that by creating and then destroying a
>>> struct director every time. Of course the API can be open for
>>> unforeseen ideas, but in this case it seems like a real stretch.
>>
>> Agreed, deleting a struct director carelessly could lead to
>> dangling pointers in other transactions.
You guys are seriously missing my point here.
The point is that we should make it simple and safe for a VMOD
to say:
Here is a director, please destroy it when...
[ ] This transaction is over
[ ] This VCL becomes cold
[ ] (Any other which might make sense)
[ ] I'l take care of it myself
And the reasone we should make it easy is *EXACTLY* to not hav
dangling pointers etc.
--
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
