[OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/MQTT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-4:
----------------------------

    Resolution: Fixed in Draft07 lines 462 on.

> Flowing MQTT messages before CONNACK is received in the client.
> ---------------------------------------------------------------
>
>                 Key: MQTT-4
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-4
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>         Environment: MQTT Client
>            Reporter: Andrew Banks
>            Assignee: Andrew Banks
>
> The MQTT Client sends CONNECT and receives  CONNACK in response. Should the client have to wait for the CONNACK or is it free to send other commands before it receives the CONNACK?
>  The advantages of allowing the client to proceed before receiving the CONNACK are:
> 1) Simpler client implementation, because the API does not have to police the connected state.
> 2) Lower latency because the client application does not have to wait for the CONNACK.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira