0 | Opening | Rémy | Rémy introduces the participants and Andre André Fatton from VerneMQ. ET-W2AT discusses pub/sub, hiearchary hierarchy and notification message format. Few parameters Using standards, to describe But we haven’t discussed the MQTT parameters for further implementation of standards as baselines. MQTT parameters. Recording of today’s meeting will be shared with ET-W2AT members. |
1 | Presentation on advanced MQTT features | Andre André Fatton, VerneMQ | André introduces Discussions: (Kai) any nodes need to subscribe to at least 2 brokers for redundancy. Question: connection failures, share data over protocol, retain retained message? (Andre) Retained message / offline messages, persistent sessions. For offline messages, persistent session is needed. Offline for one hour, estimate the volume of the messages that were missed. For the broker administrator, when all subscribers go offline , or network failed, queue size limit. If the time window is too big, no broker can do this part. MQTT is different from database.
(Rémy) shares the flow of messages in WIS2 to alert a WIS users of data availability. Persistent sessions (Hassan) WIS2 users and messages with different priorities, QoS for user/message priorities settings? (Andre) Publishers will set their QoS = 1 or 2 on their own. (Rémy) no necessary to prioritize at message level. Challenge is more on subscriber side. (Kai) It is more on dowloading side, for large volume, it is important to download by priority. (Andre) Queue Priority no needed for MQTT specification.
(Rémy) Next step is to write MQTT parameters specification in one or two pages (Hassan) MQTT Security?
|