LV-MQTT-Broker icon indicating copy to clipboard operation
LV-MQTT-Broker copied to clipboard

Native LabVIEW MQTT Broker Server

Results 82 LV-MQTT-Broker issues
Sort by recently updated
recently updated
newest added

If none of the return codes listed in Table 3.1 – Connect Return code values are deemed applicable, then the Server MUST close the Network Connection without sending a CONNACK.

requirement

If a server sends a CONNACK packet containing a non-zero return code it MUST then close the Network Connection.

requirement

If the Server does not have stored Session state, it MUST set Session Present to 0 in the CONNACK packet. This is in addition to setting a zero return code...

requirement

If the Server accepts a connection with CleanSession set to 1, the Server MUST set Session Present to 0 in the CONNACK packet in addition to setting a zero return...

requirement

If the Server rejects the CONNECT, it MUST NOT process any data sent by the Client after the CONNECT Packet.

requirement

If CONNECT validation is successful the Server MUST acknowledge the CONNECT Packet with a CONNACK Packet containing a zero return code.

requirement

If CONNECT validation is successful the Server MUST perform the processing of CleanSession that is described in section 3.1.2.4.

requirement

The Server MUST validate that the CONNECT Packet conforms to section 3.1 and close the Network Connection without sending a CONNACK if it does not conform.

requirement

Each Client connecting to the Server has a unique ClientId. The ClientId MUST be used by Clients and by Servers to identify state that they hold relating to this MQTT...

requirement

If the Keep Alive value is non-zero and the Server does not receive a Control Packet from the Client within one and a half times the Keep Alive time period,...

requirement