← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Updated: (MQTT-91) Websockets close code and reason

From
OASIS Issues Tracker <>
Date
2013-10-10T14:49:39+00:00
ID
824249055.22291381416640335.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Updated: (MQTT-91) Websockets close code and reason
[ http://tools.oasis-open.org/issues/browse/MQTT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-91:
-------------------------------

    Component/s: core

> Websockets close code and reason
> --------------------------------
>
>                 Key: MQTT-91
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-91
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Andrew Banks
>             Fix For: 3.1.1
>
>
> The use of Websockets as a transport is described in WD13 Appendix A line 1711
> Ken Borgendale suggests that this might also specify the close code and reason.
> Java J2EE 1.7 and Mozilla javascript give the ability to set these but other interfaces may not., so we can only make a recommendation.
> Normal closure ( 1000)  would be the default, but should we recommend using 1002 Protocol_Error if there is an MQTT Protocol error etc?
> What reason text should be sent if any?

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →