<div dir="ltr">Hi,<br><br>more reports... :)<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">
<div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
If you want a Zope 2 instance to run the zc.async dispatcher/worker threads, then it might be better to get the DB that zope is using. In Zope 3, there's an event you can subscribe to to get the DB. Maybe there's something similar in Zope 2 these days?<div>
</div></blockquote></div><div><br><div class="Ih2E3d"></div></div></div></div></blockquote><div><br>I found that this event it's fired since Zope2.11, but I'm using Zope2.10.6 (actually repoze.zope use this version), so I left this option<br>
</div></div>What I did to run more than 1 client instance, is to set the environment variable ZC_ASYNC_UUID from supervisord.conf<br>for each client instance.<br><br>This will start one dispatcher per instance, right? is that ok?<br>
<br>best regards<br><br>-- <br>Santiago Videla<br><a href="http://www.revolucionesweb.com.ar">www.revolucionesweb.com.ar</a><br><a href="http://www.linkedin.com/in/svidela">http://www.linkedin.com/in/svidela</a><br><br>Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que l@s tod@s somos.<br>
</div>