Ah ok Tim !
Thank you very much for your suggestion !
Paolo Patierno
Microsoft MVP
On May 3, 2014 10:31 PM, "Tim Kellogg" <> wrote:
I assumed that the timeout for the broker and client would probably be the same. It’s not specified, so I thought it would be appropriate to suggest what others are doing.
Tim Kellogg
Sr. Software Engineer, Protocols
2lemetry
605-593-7099
@kellogh
On May 3, 2014 at 2:29:01 PM, Paolo Patierno () wrote:
Hi Tim,
why do you talk about timeout in the broker ? I'm talking about the
timeout in the client to wait for PINGRESP before consider
connection lost with that broker.
Paolo Patierno
Microsoft MVP
On May 3, 2014 9:39 PM, "Tim Kellogg"
<>
wrote:
Hi Paolo,
Our broker’s timeout is set to 30 seconds. It would be nice to
specify this more clearly, or at least suggest a value.
Tim
Kellogg
Sr. Software Engineer, Protocols
2lemetry
605-593-7099
@kellogh
On May 3, 2014 at 7:36:17 AM, () wrote:
IMPORTANT NOTE: Please make sure that you are subscribed
to the mailing list before
submitting feedback with this form. For instructions on subscribing
see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=mqtt.
Comment type [editorial | technical] technical
Impact [major | minor] minor
From this :
“If a Client does not receive a PINGRESP Packet within a reasonable
amount of time after it has sent a PINGREQ, it SHOULD close the
Network Connection to the Server.”
How much is “reasonable” amount of time ?
In the actual spec 3.1 the clients has a timeout equals to
keep alive period to wait PINGRESP message.
Best regards.
Paolo Patierno
Microsoft MVP
