[OASIS Issue Tracker] Updated: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/MQTT-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-40:
-------------------------------

    Component/s: edits
                     (was: core)

This looks like an editorial issue. The input specification is fairly clear with respect to Client, Server, Publisher and Subscriber.
I think the best way forward is to prefer the terms Client and Server and add Publish(er) Subscribe(r) where is adds value to the narrative.

There is an open edits issue to improve general terminology which to should remove any confusion (MQTT-53)

> Should MQTT Publisher and MQTT Subscriber be differentiated
> -----------------------------------------------------------
>
>                 Key: MQTT-40
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-40
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: edits
>    Affects Versions: 3.1.1
>            Reporter: Nick O'Leary
>             Fix For: 3.1.1
>
>
> The spec used to talk about MQTT Clients. It now talks about MQTT Publishers and MQTT Subscribers - as if they are completely different things. But ultimately, an MQTT Publisher can subscribe to things and an MQTT Subscriber can publish to things. 
> I'm not sure it is helpful to introduce the idea they are different entities when they are not. It implies you need two different clients if you want to do both pub and sub - a misapprehension we've had to respond to on the mailing list in the past.

-- 
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