-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 11/16/2015 03:31 PM, Dridi Boukelmoune wrote: >>> 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. > > Maybe I should document a rule of thumb such as never deleting a > struct director that is made available to VCL code. If you delete > the director/backend underneath it's fine. You can simply get a > NULL director from the resolve function.
Mmmm, this may be a misunderstanding, the context was PRIV_* scopes for backends, such as PRIV_TASK or PRIV_TOP. I would argue that creating backends at the beginning of such a scope and removing them at the end is such an unlikely solution that we should consider not supporting it. But it sounds like you're saying backends should not be deleted under any circumstances. That I don't agree with. What should I do about backends that cease to exist, in a context where it's not workable to reload a new static backend configuration? That's what I want the runtime backend delete for. Best, Geoff - -- ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstraße 32 22301 Hamburg Tel +49 40 2880 5731 Mob +49 176 636 90917 Fax +49 40 42949753 http://uplex.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWSfkxAAoJEOUwvh9pJNURhDAQAJlpbpZFqOyT3A1+VGFdAXaE A5YTUf7tlrIajQZlHfAlR26XxgEfB2pUsUDuVPo7SUvcht4MrLnBy/sZXOMdNt15 Mz/qv2ilB5oF80Lih6E8TB52aghExPfYUQ26bEtKGRaAVNcB1jYhn8NF5SmU36Nn eTbpbUuo5PdfN+HQy4i5sQSPJQTWPFy7Bfbzhs/8hKVmyG9ZpT5bwQC3InPLj9RY zEYDNrzF/JD797yz+ppdpEscFZHIMVZsr46wmyhD+8ukghttlvH5XWI32gU3nHuy wkLa7r1heIjetBf0Jfz08UHpQXJ+aGIcGB81bhA0jocjSooAFc4dcgs/BkxYME/5 2nkTk1ZiwGsAnNlhV9URl0vF/eHt68a6Fy4ur/HQoBmvMCZs6hRKhZYynatOAtqw gmwR7jSntpDjU28hIpeNuUOR7M52P6OwZxZwh+7eslSfnqlJ6bDlXmA1jbYCyCRq RSEcWtoo4twskEUi4zHfgznWS1QF2CC7ZNRj82QLx9V/cWGuhaHmNXkTQOYMMrWQ iZDC+qpHMTMWVllKcHUi9cJde9x0hO5d+p/0//ysnF/PRnidSHns8JUHra3fpqaC 3Nx8lqEWO88HFtFCO04a+POcjo89X4KH1omDfpk5Oj1HVjof9TMEKmPhkbqUSSra 5tUoOKyes30T/U+PT1MA =lFpm -----END PGP SIGNATURE----- _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
