<div dir="ltr"><div><div><div>Hi Michael,<br><br></div>Thank you very much for the information. I am wondering why if IP for first and second connections are the same (in the scenarios in which the connection lost and resumed almost immediately via same network) the first connection gets closed almost immediately after the second connection was established.<br>
<br><br></div>Regards,<br></div>--Wong Liong Hung<br><div><div><div><div><br><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 3, 2013 at 5:16 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On nov 2, 2013, at 5:39 PM, L H, Wong <<a href="mailto:lhwong@gmail.com">lhwong@gmail.com</a>> wrote:<br>
<br>
> I am aware of the heartbeat setting. However, my application is running on mobile phone I afraid that if I set the value to lower value like 10s it will consume more battery power and also cause higher data usage.<br>
<br>
This is an understandable concern but there are no other options.<br>
<br>
I’d suggest using a value of 20 or so. This means a little bit of data (about a dozen of bytes)<br>
will be sent roughly every 10 seconds. There will be no new threads created or significant<br>
amounts of CPU consumed, so net impact on energy consumption and traffic<br>
likely will be very small.<br>
--<br>
MK<br>
<br>
Software Engineer, Pivotal/RabbitMQ<br>
<br>
<br>
</blockquote></div><br></div>