Oh I misunderstood the wording on the configuration: I read it as "the broker would send a connection.tune to the client every 10 minutes by default asking the client if it wanted to renegotiate heartbeats".<div>
<br></div><div>Thanks for the�clarification.<br><div><br></div><div>-Alan<br><br><div class="gmail_quote">On Wed, Nov 21, 2012 at 11:12 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alan,<div class="im"><br>
<br>
On 21/11/12 15:57, Alan Antonuk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Looking for a bit more information on these new heartbeats that v3<br>
implements:<br>
<br>
- For the connection.tune method that gets sent to the client every<br>
${heartbeat} seconds:<br>
</blockquote>
<br></div>
connection.tune/tune-ok gets sent just once, during connection establishment. Always has been that way.<br>
<br>
heartbeat frames have their own frame type. And should only be transmitted on channel 0. Again, this hasn't changed.<br>
<br>
The only change in 3.0 is that the server, instead of always proposing a heartbeat interval of 0 (i.e. on heartbeats), a) proposes an interval of 10 minutes by default, and b) makes that value configurable.<br>
<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote></div><br></div></div>