Remote deployment is very useful, but would be more practical if some features exists:
- In an environment with many connected users and multiple nodes, when it is detected that a new version is available, show a message that the user would have X minutes or force to close the application. Hyper Server would send a message to the TUniServerModule of each application that could display that message to the user. - Capture remotely the information of several servers running Hyper Server, and thus with an administration centralized know to be there are many crashes and excesses of memory consumption, close sessions remotely. - In case of errors in new executables, to be able to return an old version of the application without having to recompile, it would be a rollback. - Remotely be able to restart or quit Hyper Server. It could easily be done when it detects a particular file in the deploy folder. Example, when the file 'reboot.dep' exists, all applications of the nodes would be closed. Or when the 'quit.dep' file exists, terminate the 'hyper_server.exe' application, and so it would be possible to remotely update the hyper server executable.
Farshad Mohajeri, is it possible to create these options?