DATE: 26 APR 2017

N2O: Protocol Server for MQTT

INTRO

The n2o defines the way you define, confifure and run arbitrary applications and protocols inside some hosts, into which n2o is injected. They can be cowboy and emqttd. Each application can spawn its instance in own way, like web pages spawn WebSocket connections, workflow engines spawn business proceseses and chat application spawns roster and chatroom processes. This is managed by protocols.

PROTOCOLS

While all application protocols in the system are desired to be placed in the single effectful environment or same error handling path, n2o defines single protocol loop for all applications in its federation of protocols.

In core bundle n2o is shipped with NITRO and FTP protocols which allows you to create real-time web applications with binary-based protocols, priving also robust and performant upload client and file transfer protocol. For bulding web based NITRO applications you need to include nitro dependency.

CONFIG

[{n2o,[{formatter,bert}, {json,jsone}, {pickler,n2o_secret}, {erroring,n2o}, {protocols,[n2o_ftp,n2o_nitro]}, {filter,{n2o_proto,push}}, {timer,{0,10,0}}]}].

Also you may refer to: n2o_format, n2o_proto, n2o_async, n2o_ftp, n2o_nitro,

© Synrc Research Center