[OASIS Issue Tracker] Updated: (MQTT-160) Weak definition.of Server

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

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

Andrew Banks updated MQTT-160:
------------------------------

    Proposal: 
Replace the definition of Server in section 1.2 Terminology line 249 with:

A program or device that acts as an intermediary between Clients which publish 
Application Messages and Clients which have made Subscriptions.
A Server:
- Accepts the Network Connections from Clients. 
- Accepts Application Messages published by Clients
- Processes the Subscribe and Unsubscribe requests from Clients 
- Forwards Application Messages that match Client Subscriptions.

> Weak definition.of Server 
> --------------------------
>
>                 Key: MQTT-160
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-160
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>         Environment: Technical
>            Reporter: Patrick Durusau
>
> In Terminology section:
> Weak definition of [MQTT] Server. Unclear what general functions the Server is supporting. This definition depicts (vague) relationships of Server with other components, ( "accept connection from Client" "intermediary between X and Y".) which is useful but not sufficient for the definition of such a central artifact subject to conformance.  The Client definition is better..

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