Sure just give me 5 minutes :-) As you said it that work would be HUGE. Simple said it's a complete re-write of the app. If we're gonna do this? Maybe. When? No date for it. We are design a "distributed" way to work with Servers Alive, and IF this ever gets to the point of real dev. then this will be a nice test case for a (HUGE) step further being a splitt of interface and check (or as you said it a backend and frontend)
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Lambrecht Pieter Sent: Wed Sep 17 5:09 PM To: [EMAIL PROTECTED] Subject: [SA-list] 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]
<<attachment: winmail.dat>>
