Re: Preventing multiple instance standalone desktop gui applications
From: Gordon Beaton (not_at_for.email)
Date: 09/28/04
- Next message: Paul Lutus: "Re: JPasswordField setText depreciation?"
- Previous message: Paul Lutus: "Re: grassfire algorithm in java"
- In reply to: Kent Yang: "Re: Preventing multiple instance standalone desktop gui applications"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Sep 2004 08:39:21 +0200
On 27 Sep 2004 16:38:38 -0700, Kent Yang wrote:
> 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.
In practice, reusing a server port is never a problem.
Even if the ServerSocket constructor doesn't set SO_REUSEADDR (i.e.
setReuseAddress(true)) before binding the socket, you can. Although I
believe it does by default.
/gordon
-- [ do not email me copies of your followups ] g o r d o n + n e w s @ b a l d e r 1 3 . s e
- Next message: Paul Lutus: "Re: JPasswordField setText depreciation?"
- Previous message: Paul Lutus: "Re: grassfire algorithm in java"
- In reply to: Kent Yang: "Re: Preventing multiple instance standalone desktop gui applications"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
