Did emitter support clientid as MQTT
shushenghong opened this issue · comments
in MQTT protocol specification
3.1.3.1 Client Identifier (ClientID)
The Client Identifier (ClientID) identifies the Client to the Server. Each Client connecting to the Server has a unique ClientID. The ClientID MUST be used by Clients and by Servers to identify state that they hold relating to this MQTT Session between the Client and the Server [MQTT-3.1.3-2]. Refer to section 4.1 for more information about Session State.
If the ClientID represents a Client already connected to the Server, the Server sends a DISCONNECT packet to the existing Client with Reason Code of 0x8E (Session taken over) as described in section 4.13 and MUST close the Network Connection of the existing Client [MQTT-3.1.4-3]. If the existing Client has a Will Message, that Will Message is published as described in section 3.1.2.5.
Did emitter treat clientid like this?
this is useful when the same person login to the chatroom, open multiple webpages sametime eg.
Not right now, as we don't currently support the distributed cluster sessions. Hence, emitter is creating it's own connection ID and associates this with the connection.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.