[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-271) Describing small device limitations, aka "the Arduino problem"
[ https://issues.oasis-open.org/browse/MQTT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62254#comment-62254 ] Nicholas O'Leary commented on MQTT-271: --------------------------------------- Following review at the April F2F meeting, it was proposed that all of the considerations this JIRA raises would be covered by MQTT-276 - https://issues.oasis-open.org/browse/MQTT-276 - enhancements for large scale distributed systems. This includes: - qos limits - message size limits - flow control (nb, some of those are linked from MQTT-276 to other JIRAs) If that's agreed, we can focus efforts there and close this JIRA. > Describing small device limitations, aka "the Arduino problem" > -------------------------------------------------------------- > > Key: MQTT-271 > URL: https://issues.oasis-open.org/browse/MQTT-271 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: futures > Affects Versions: 3.1.1 > Environment: Very small device implementations. > Reporter: Ian Craggs > > Small devices, like the original Arduino, may have very limited resource, like 16k of RAM, or less. For such devices, limiting the storage used by MQTT is very important. > They may not even be able to process a message of 30k, for instance, at all. If it were sent at QoS 1 or 2, it has to be read in before subsequent messages are received. > At the moment, it is a server admin task, or application design task, to make sure that messages bigger than a device can handle are not sent to it. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]