Support of sleeping clients about emqx-sn HOT 4 CLOSED

Developing this feature now. Please be patient since too many TODOs in my list.

from emqx-sn.

@jpmzometa This bug has been fixed in v2.3-beta1.

from emqx-sn.

@jpmzometa sleeping device will be added into next official release.

from emqx-sn.

Hi. I've been playing around with the sleeping client implementation. It does not work as expected. A client doing a CONNECT to the gateway, SUBSCRIBE to a topic, and DISCONNECT with a duration (i.e. going to sleep) works correctly. However, every time the client sends a PINGREQ (client awake) message, it gets from the gateway all the previous messages that have been published (in the topics subscribed by the client) since the client went to sleep via the DISCONNECT with duration.

Put in another words, if there are buffered messages for the client in the gateway (that is, for the topics for which the client has subscribed), after a PINGREQ from the client (i.e. client is awake), the gateway should send all buffered messages and at the end a PINGRESP, and the gateway should clear its buffer (assuming all messages satisfied the QoS). If the client sends a new PINGREQ, the gateway should just reply with a PINGRESP if there are no new messages. At the moment, it appears the buffered messages are not cleared in the gateway (i.e. each new message is added to the buffer, and all messages in the buffer are sent to the client every time a PINGREQ arrives from the client).

from emqx-sn.