Looping on connect-disconnect

[Andrea]

Hi I've a question about the intended behaviour of a broker in a particular condition.
I've a client (Paho J) that loop on CONNECT and DISCONNECT to a broker.
 The specs says that on the client side,the client send a DISCONNECT message and then  must close the network connection.
 Now my question is, supposing the broker is slow (for any reason) to process the client DISCONNECT resquest, and while it's still processing the request the client has already closed the connection and quickly opens anotherone with the server and sends a CONNECT message.
 Which should be the behaviour of the broker? The new CONNECT should be threated as when a broker receive a second CONNECT and should close and drop the first, or should send some error code the client because it's still processing the previous DISCONNECT?

Thanks in advance for any clarification.

 Andrea Selva

[Nicholas O'Leary]

The new connection should 'win' and the old connection closed.

Nick

--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To post to this group, send email to mq...@googlegroups.com.
Visit this group at https://groups.google.com/group/mqtt.
For more options, visit https://groups.google.com/d/optout.