Re: Preventing multiple instance standalone desktop gui applications
From: Kent Yang (kent.yang_at_gmail.com)
Date: 09/28/04
- Next message: George W. Cherry: "Re: Where is Roede??"
- Previous message: David Scurrah: "Re: Start a windows program"
- In reply to: Kent Yang: "Preventing multiple instance standalone desktop gui applications"
- Next in thread: Gordon Beaton: "Re: Preventing multiple instance standalone desktop gui applications"
- Reply: Gordon Beaton: "Re: Preventing multiple instance standalone desktop gui applications"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 27 Sep 2004 16:38:38 -0700
Thanks everyone for all the great responses.
My concern with socket approach is that one port will be dedicated to
the application. I know its only one port / resource. The other
concern is that I had socket applications that crash, and because it
wasn't close properly, the socket can not be reused for a little while
(probably because the OS resource not cleanup). So the port gets lock
out until a system restart or until the OS catches up.
The sample example posted by Jean-Francois Briere works great. I owe
you a beer.
It may sound like a strange request for this type of application
feature but there are instances where this is beneficial to very basic
users. Also, precedence have set by applications such as IDE(s),
JBuilder for example. I am guessing they use some native code to
bring up the current running instance.
Thanks again everyone for all the great responses.
Kent
- Next message: George W. Cherry: "Re: Where is Roede??"
- Previous message: David Scurrah: "Re: Start a windows program"
- In reply to: Kent Yang: "Preventing multiple instance standalone desktop gui applications"
- Next in thread: Gordon Beaton: "Re: Preventing multiple instance standalone desktop gui applications"
- Reply: Gordon Beaton: "Re: Preventing multiple instance standalone desktop gui applications"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|