[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions?
[ http://tools.oasis-open.org/issues/browse/MQTT-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34668#action_34668 ]
Raphael Cohen commented on MQTT-58:
-----------------------------------
Please see above for why I really don't like multiple delivery of the same message. If a client really wants this behaviour they can "Just run multiple connections". I'm not convinced about the performance angle, but if filtering for only once messaging can be made using a short cut OR ( || to C programmers) then it shouldn't hurt - and should be near identical. What this approach precludes is a dispatch queue per filter expression subscribed, but that seems minor and wouldn't be optimal in most cases (as it requires more filter evaluations, filter objects, queues, etc).
Regardless of that view, I feel this is a SHOULD / MUST for one way or the other - otherwise we will produce a protocol that's got a rather large variation in what can be expected, and it'll be impossible to change this behaviour in any new version.
> How many messages are received for overlapping subscriptions?
> -------------------------------------------------------------
>
> Key: MQTT-58
> URL: http://tools.oasis-open.org/issues/browse/MQTT-58
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.1.1
> Reporter: Allan Stockdill-Mander
> Fix For: 3.1.1
>
>
> A client has subscribed to a/+ with QoS2 and a/b with QoS1. A message is published to a/b. Does the client receive one or two messages? If one which QoS would apply?
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]