Endpoints
66 |67 | Here is a list of types of endpoints which are supported by EMQ and accessible to N2O apps: 68 | WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. 69 | Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, 70 | but for IoT and MQTT applications it could be served through UDP or SCTP protocols, 71 | providing application level message delivery consistency. 72 | By using MQTT as a transport we extend the supported set of endpoint protocols. 73 |
74 |MQTT
77 |EMQ is an open-source MQTT broker implemented by Feng Lee. 78 | N2O is EMQ compatible plugin that acts as predefined MQTT clients that form 79 | a ring of virtual nodes, process all the protocol requests, 80 | and answer to client topics according to classical RPC over MQ schema. 81 | This list of modules forms a core of N2O that is common for 82 | both MQTT and WebSocket versions: 83 |
84 |
94 | $ mad app zero review
95 | $ cd review
96 | $ mad dep com pla rep
97 | $ open http://127.0.0.1:8000
98 |
99 | WebSocket
110 |COWBOY is small, fast, and modern HTTP server implemented by Loïc Hoguin. 111 | In this version, N2O loop is integrated as WebSocket cowboy 112 | handler that routes all incoming messages to N2O. 113 | The list of WebSocket specific modules:
114 |-
115 |
- n2o_cowboy — COWBOY API 116 |
- n2o_ws — WebSocket DHT Processing Node 117 |
120 | $ mad app nitro sample
121 | $ cd sample
122 | $ mad dep com pla rep
123 | $ open https://127.0.0.1:8001/app/index.htm
124 |
125 | Protocols
129 | 134 |Services
137 |-
138 |
- n2o_session — ETS sessions backend 139 |
- n2o_secret — AES/GCM-256 encoder/decoder 140 |
- n2o_gproc — GPROC MQ backend 141 |
- n2o_syn — SYN MQ backend 142 |
JavaScript
146 |-
147 |
- utf8.js — UTF-8 encoder/decoder 148 |
- zlib.js — ZLIB inflate algorithm 149 |
- ieee754.js — IEEE-754 encoder/decoder 150 |
- bert.js — BERT encoder/decoder 151 |
- n2o.js — N2O protocol looper 152 |
- heart.js — HEART protocol 153 |
- nitro.js — NITRO protocol 154 |
- ftp.js — FTP protocol 155 |
- mq.js — MQTT client 156 |
SPEC
160 |
163 | -type n2o() :: #bert{} | #json{} | #binary{} | #default{}.
164 | -type cx() :: #cx{}.
165 | -type formatter() :: binary | json | bert | text | default | atom().
166 | -type response() :: { formatter(), binary() }.
167 |
168 | -record(ok, { data :: term() }).
169 | -record(error { data :: term() }.
170 | -record(reply, { msg :: n2o(), req :: term(), ctx :: cx() } ).
171 | -record(unknown, { msg :: n2o(), req :: term(), ctx :: cx() } ).
172 |
173 | -spec start(#pi{}) -> {pid(),term()} | #error{}.
174 | -spec stop(term(),atom()) -> #pi{} | #error{}.
175 | -spec proc(atom(),#pi{}) -> term().
176 | -spec info(term(),term(),#cx{}) -> #reply{} | #unknown{}.
177 |
178 | -record(pi, { name :: term(),
179 | table :: atom(),
180 | sup :: atom(),
181 | module :: atom(),
182 | state :: term() }).
183 |
184 | -record(cx, { handlers = [] :: list({atom(),atom()}),
185 | actions = [] :: list(tuple()),
186 | req = [] :: [] | term(),
187 | module = [] :: [] | atom(),
188 | lang = [] :: [] | atom(),
189 | path = [] :: [] | binary(),
190 | session = [] :: [] | binary(),
191 | formatter = bert :: bert | json | atom(),
192 | params = [] :: [] | list(tuple()),
193 | node = [] :: [] | atom(),
194 | client_pid = [] :: [] | term(),
195 | state = [] :: [] | term(),
196 | from = [] :: [] | binary(),
197 | vsn = [] :: [] | binary() }).
198 |
199 | -type memtable() :: atom().
200 | -spec encode(tuple()) -> binary().
201 | -spec decode(binary()) -> tuple().
202 | -spec session(term(),term()) -> term().
203 | -spec session(term()) -> term().
204 | -spec cache(memtable(),term(),term()) -> term().
205 | -spec cache(memtable(),term()) -> term().
206 |
207 | 209 |
