Title: Split Salive in a frontend and a backend

Hi Dirk,

This questions looks simple but I guess it is going to be a huge work.

Is it possible to split Salive in a Frontend GUI and a backend NON-Gui.
The backend is the service part that does the checking, and totally independent of the frontend.
The frontend just checks the service status and the monitoring database.
Traffic between the front and backend has to be IP  (TCP/UDP) and has to be encrypted...

This would solve the Terminalserver issue that you need to connect to the desktop of the Server to manage Salive
And, it would allow an easier (centralized) remote management.
If you have more then one server running Salive, it could be centrally managed on one workstation.

Any luck this is going to be implemented ?

Pieter

Pieter Lambrecht
ICORDA N.V.
Brugsevaart 32
9030 Gent
Tel: +32 9 227 66 76
Fax: +32 9 227 97 45
Email: [EMAIL PROTECTED]


Reply via email to