[master] 2c4cb15 More details on event considerations for directors

[Dridi Boukelmoune]

commit 2c4cb155e59e398d989a38473b37d6f9b6c403f5
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Tue Aug 18 15:06:34 2015 +0200

    More details on event considerations for directors

diff --git a/doc/sphinx/reference/directors.rst b/doc/sphinx/reference/directors.rst
index 8a16c87..c4e6ecb 100644
--- a/doc/sphinx/reference/directors.rst
+++ b/doc/sphinx/reference/directors.rst
@@ -114,7 +114,11 @@ to keep track of backends and objects have a VCL name you can reuse for the
 director. It is also true for *cluster* directors that may reference native
 backends.
 
-Finally, Varnish will take care of event propagation for *all* native backends.
+Finally, Varnish will take care of event propagation for *all* native backends,
+but dynamic backends can only be created when the VCL is warm. If your backends
+are created by an independant thread (basically outside of VCL scope) you must
+subscribe to VCL events and watch for VCL state (see
+:ref:`ref-vmod-event-functions`).
 
 
 .. _ref-writing-a-director-cluster: