develop
master
fixes
release/2.0
release/1.6
dynamic-bridge
release/1.5
debian
debian-mosquitto
v2.0.15
v2.0.14
v2.0.13
v2.0.12
v2.0.11
v1.6.15
v2.0.10
v2.0.9
v1.6.14
v1.5.11
v2.0.8
v2.0.7
v1.6.13
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.5.10
v1.6.12
v1.6.11
v1.6.10
v1.6.9
v1.6.8
v1.6.7
v1.6.6
v1.5.9
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.1
v1.6
v1.5.8
v1.5.7
v1.5.6
v1.5.5
v1.5.4
v1.5.3
v1.5.2
v1.5.1
v1.5
v1.4.15
v1.4.14
v1.4.13
v1.4.12
v1.4.11
v1.4.10
v1.4.9
v1.4.8
v1.4.7
v1.4.6
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.3.2-not-blessed
v1.3.3-not-blessed
v1.3.4-not-blessed
v1.3.5-not-blessed
v1.4
${ noResults }
1 Commits (c6aac741c2c294b5e2b469ee8c05c1aad5c80c59)
Author | SHA1 | Message | Date |
---|---|---|---|
|
c6aac741c2 |
broker: support byte based queueing
Limiting queued message depth purely based on message count is hard to control for memory constrained devices. The size of messages can vary wildly, from a few bytes, to a few kilobytes. Support a new max_queued_bytes option, and drop packets when the first limit is reached. Option defaults to 0 (disabled) by default. Support also a max_inflight_bytes variable, with similar behaviour. Fixes (partof) https://github.com/eclipse/mosquitto/issues/100 This pulls up some helper routines for calculating whether to allow inflight or queuing, resolving some inconsistences in connection resumption. Signed-off-by: Karl Palsson <karlp@etactica.com> |
9 years ago |