[CLOSED] Make UMS a singleton / limit to a single instance
Posted: Fri Mar 08, 2013 8:17 pm
An old suggestion I made for PMS that applies to UMS as well:
Can you put in code to limit UMS to a single instance?
I run it as a service, but if I want to mess with the settings, I launch the GUI - which in turn starts another instance of UMS. If I launch the GUI again, another instance pops up.
It would be nice if I could get to the GUI to change settings without having to launch additional instances. Would also be nice if changes made in the GUI were picked up by the service without having to restart.
-----
Looks like there are some implementations here:
http://yuvadeveloper.blogspot.com/2009/ ... -java.html
It would be nice if you could launch UMS and if an instance (or the service) was already running, it just brought up the GUI.
Additionally if you clicked on the restart HTTP server and if PMS was running as a service, restarting the service.
Can you put in code to limit UMS to a single instance?
I run it as a service, but if I want to mess with the settings, I launch the GUI - which in turn starts another instance of UMS. If I launch the GUI again, another instance pops up.
It would be nice if I could get to the GUI to change settings without having to launch additional instances. Would also be nice if changes made in the GUI were picked up by the service without having to restart.
-----
Looks like there are some implementations here:
http://yuvadeveloper.blogspot.com/2009/ ... -java.html
It would be nice if you could launch UMS and if an instance (or the service) was already running, it just brought up the GUI.
Additionally if you clicked on the restart HTTP server and if PMS was running as a service, restarting the service.