This repository has been archived by the owner on Aug 11, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Life Cycle
Rick Zhou edited this page Jan 24, 2018
·
4 revisions
- open a port as a dslink responder server
- starts broker
- connects to broker as a dslink client
- starts dslinks, and tell dslinks to connect to broker
- loads broker configs
- loads dll/so modules
- check each module for the component
- fill in the essential strand component that's not defined in modules
- logger
- authentication
- authorization
- storage
- initialize the modules
- check if any module want to register a responder node under
modules
node
- load data from storage
- node structure
- qos queue data
- open tcp port and start beast web server
- check if any module want to register an end point in the web server