Today, all logic is done in the browser, to make alarm-development really fast. This, however, limits the use of the very cool "map-handler" logic that is what makes Gondul really awesome.
To leverage this, let's make an API that runs node.js, imports nms-map-handlers.js and nms-data.js, sets up the same nmsData pollers as is done in js/nms.js:initNMS(), then exposes the map handler functions through an API.
This should allow any client, e.g. a mobile phone, to query of the health status of a single switch. Longer-term is support for multiple switches.
Today, all logic is done in the browser, to make alarm-development really fast. This, however, limits the use of the very cool "map-handler" logic that is what makes Gondul really awesome.
To leverage this, let's make an API that runs node.js, imports nms-map-handlers.js and nms-data.js, sets up the same nmsData pollers as is done in js/nms.js:initNMS(), then exposes the map handler functions through an API.
This should allow any client, e.g. a mobile phone, to query of the health status of a single switch. Longer-term is support for multiple switches.