01-06-2015 06:18 PM
Hi, Rob -
We've observed that as long as the first launch of the server is via its controller interface, then subsequent method calls on the controller interface seem to reuse the already-launched server. This seems to be true even if different applications / processes subsequently use the controller interface methods. As such, we're considering a simple workaround: We'll start up the server using a command-line application that makes some minimal and harmless use of the controller interface, just to get the server launched. The theory (and hope) is that all subsequent usage of the controller interface will bind to this instance of the server. Note that this is not quite the same as launching the server directly from the command line, which was my original desire; but it's essentially equivalent for our purposes.
I will try to post again with further findings as we test this approach. Thanks again for your help!
Barry
01-07-2015 12:08 PM
No problem. I hope it works, I'm interested in what you will find.