robot/emqx
1
0
Fork 0
mirror of https://github.com/emqx/emqx.git synced 2026-03-13 08:02:20 +08:00
Code Issues Packages Projects Releases Wiki Activity
Page: Session Design
Pages
$SYS Topics AC ACL Design Alarm Authentication Benchmark Bridge Client State Cluster Design Cluster Configuration Dashboard Design EMQ X Roadmap Event Design FAQ Firewall Get Started HTTP Publish Home Hooks Design Improve the Session Queue Design Inflight Window of Broker Installation Overview Plugin Design Presence PubSub Design PubSub Sequence Queue Design Quick Start Rate Limiting and Flow Control Rewrite Session Design Topic Design Trace User Guide WebSocket Zone based authentication ACL benchmark for 0.10.4 release benchmark for 0.12.0 release benchmark for 0.13.0 release eMQTT Design emqttd and rabbitmq emqttd.init etc emqttd.config for benchmark etc vm.args for benchmark linux kernel tuning
Clone
4
Session Design
Feng Lee edited this page 2015-06-08 14:19:15 +08:00
Unescape Escape
Table of Contents
This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Protocol Specification

If CleanSession is set to 0, the Server MUST resume communications with the Client based on state from the current Session (as identified by the Client identifier). If there is no Session associated with the Client identifier the Server MUST create a new Session. The Client and Server MUST store the Session after the Client and Server are disconnected[MQTT-3.1.2-4].

CleanSession set to 0, the Server MUST store further QoS 1 and QoS 2 messages that match any After the disconnection of a Session that had subscriptions that the client had at the time of disconnection as part of the Session state

It MAY also store QoS 0 messages that meet the same criteria.

Session State in the broker consists of:

  1. The Client’s subscriptions.
  2. inflight qos1, qos2 messages sent to the client but unacked, QoS 1 and QoS 2 messages which have been sent to the Client, but have not been completely acknowledged.
  3. inflight qos2 messages received from client and waiting for pubrel. QoS 2 messages which have been received from the Client, but have not been completely acknowledged.
  4. all qos1, qos2 messages published to when client is disconnected. QoS 1 and QoS 2 messages pending transmission to the Client.
  5. Optionally, QoS 0 messages pending transmission to the Client.

Session State in the client consists of:

QoS 1 and QoS 2 messages which have been sent to the Server, but have not been completely acknowledged.

QoS 2 messages which have been received from the Server, but have not been completely acknowledged.

session manager


%% lookup sesssion
emqtt_sm:lookup_session(ClientId)

%% Start new or resume existing session
emqtt_sm:start_session(ClientId)

%% destroy session, discard all data
emqtt_sm:destory_session(ClientId)

%% close session, save all data
emqtt_sm:close_session(ClientId)

session supervisor

usage?

session

%%system process
process_flag(trap_exit, true),

session:start()
session:subscribe(
session:publish(
session:resume(
session:suspend(
%%destory all data
session:destory(
%%save all data
session:close()

sm and session

sm manage and monitor session

client and session

client(normal process)<--link to -->session(system process)

Version: 1.0(Draft) Author: Feng Lee feng@emqx.io