I think, this approach must turn the most reliable one. The standard
technique here is for the first instance simply to listen to a certain
obscure port by means of a rudimentary home-made tcp server and when a
user launches more instances they try to identify whether there is
already an instance in existence and if so they exit at once and that
first instance creates and shows additional "main" windows. This is
actually a very efficient and preferable way to run multiple desktop
Java apps of the same family.
Andriy.
Andrus Adamchik wrote:
>
> So another solution might be a multi-window Modeler. Shouldn't be too
> hard to implement. When a Modeler starts, it sends a message out to
> see if the Modeler is already running on this machine (JavaGroups can
> help in instance discovery). If there is none, Modeler starts as
> usual. If there is another instance, it is activated (main window is
> brought to the front), and if there is a project to be opened, a new
> window is opened in that other JVM. I believe a lot of native desktop
> apps work like that.
>
This archive was generated by hypermail 2.0.0 : Tue Nov 02 2004 - 20:11:43 EST