<div dir="ltr">Hi Nikola.<div><br></div><div style>php-amqplib doesn&#39;t support heartbeats right now, but I was just reading the source code trying to understand how/where to add them.</div><div style><br></div><div style>
I would try to cook a new version of the lib with support for heatbeats. At least to be able to reply to the server when it sends heartbeats to the client.</div><div style><br></div><div style>Sending heartbeats to the server to see if it is still there is harder with PHP, since there are no timeouts as with Javascript.</div>
<div style><br></div><div style>Regards,</div><div style><br></div><div style>Alvaro</div><div style><br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 19, 2013 at 5:35 PM, Nikola Savic <span dir="ltr">&lt;<a href="mailto:niks@osic.rs" target="_blank">niks@osic.rs</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div><br>
      Hmm ... I&#39;ll look into using basic.consume with two channels like
      you suggest.<br>
      <br>
      There is one more channel that we use :( Direct channel by which
      worker process (consumer) sends ECHO message to itself, because we
      couldn&#39;t make php-amqplib recognize that RabbitMQ has gone away. <br>
      <br>
      Alvaro, is there support for AMQP heartbeat in php-amqplib? I was
      not being able to find and activate it :(<div><div class="h5"><br>
      <br>
      On 05/19/2013 05:26 PM, Michael Klishin wrote:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">
      <div dir="ltr">
        <div class="gmail_extra">2013/5/19 Nikola Savic <span dir="ltr">&lt;<a href="mailto:niks@osic.rs" target="_blank">niks@osic.rs</a>&gt;</span><br>
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">We&#39;re
              not using basic_consume, since we must monitor two
              different channels/exchanges (one direct and one fannout).
              This is because workers must get messages (task related)
              by direct queue, and broadcasts over fannout</blockquote>
          </div>
          <br>
          You should be able to do this easily with any client using
          basic.consume.<br>
          <br clear="all">
          <div>Also, sounds like a suitable use case for
            exchangeo-to-exchange bindings:</div>
          <div><br>
          </div>
          <div><a href="http://www.rabbitmq.com/e2e.html" target="_blank">http://www.rabbitmq.com/e2e.html</a><br>
          </div>
          -- <br>
          MK<br>
          <br>
          <a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
          <a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><div class="im"><pre>_______________________________________________
rabbitmq-discuss mailing list
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
    </div></blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>