98 messages

org.oasis-open.lists.mqtt [All Lists]

2013 May [All Months]

Page 1 (Messages 1 to 25): 1 2 3 4

[mqtt] Groups - OASIS_MQTT_TC_minutes_25042013.pdf uploaded - Richard Coppen
[mqtt] Groups - Event "MQTT TC Meeting (Conference Call)" added - Richard Coppen
[mqtt] [OASIS Issue Tracker] Created: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Created: (MQTT-2) UTF-8 for will messages - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? - OASIS Issues Tracker
[mqtt] Groups - Event "MQTT TC Meeting (Conference Call)" modified - Richard Coppen
[mqtt] [OASIS Issue Tracker] Updated: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? - OASIS Issues Tracker
[mqtt] Groups - Event "MQTT TC Meeting (Conference Call)" added - Richard Coppen
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Issue Comment Edited: (MQTT-11) Length of client Identifier - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? - OASIS Issues Tracker
Re: [mqtt] [OASIS Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? - Allan Stockdill-Mander
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-9) If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet. - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. - OASIS Issues Tracker
[mqtt] Groups - Event "MQTT TC Meeting" added - Richard Coppen

Page 1 (Messages 1 to 25): 1 2 3 4