New scheme to deal with listeners, there is a Listener object for each listener encap...
authorNick Downing <nick@ndcode.org>
Tue, 4 Dec 2018 06:46:40 +0000 (17:46 +1100)
committerNick Downing <nick@ndcode.org>
Tue, 4 Dec 2018 06:46:40 +0000 (17:46 +1100)
commite1b525a9f5d5c0e384b9d365173802978fe177f7
tree7b2e9ecf44b9e579ab9aee199b7ecf0196213b9d
parentfbc1e0444fd6c86968baf7cd9bb1d2fbfd3acc87
New scheme to deal with listeners, there is a Listener object for each listener encapsulating the logic for stopping and starting that used to be in Server.refresh_config(), listeners are stored in Resources object with a reference count, Server.start()/stop()/kick() are called on configuration change/timer, which may or may not call each Listener.start()/stop() depending on the reference counts
Listener.js [new file with mode: 0644]
Resources.js
Server.js
Site.js
_config/server.jst
cli.js