OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects


    [ https://issues.oasis-open.org/browse/MQTT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59277#comment-59277 ] 

Peter Niblett commented on MQTT-262:
------------------------------------

In the security section, we need to warn people to control access to a client ID - in other words authenticate a user first and then check that they are entitled to use the client ID that they provided. That way you avoid a malicious user stealing the client ID and forcing the genuine user off.

> Clarify will messages if server disconnects
> -------------------------------------------
>
>                 Key: MQTT-262
>                 URL: https://issues.oasis-open.org/browse/MQTT-262
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Raphael Cohen
>            Assignee: Raphael Cohen
>
> If a server disconnects a connection because a second client has connected with the same client id, should the first connections' will message be sent? I would argue it should, because this scenario is intended to reflect 'stuck' and 'hung' clients.



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