Re: Force quit without monitor
Re: Force quit without monitor
- Subject: Re: Force quit without monitor
- From: Lachlan Deck <email@hidden>
- Date: Sun, 6 May 2007 12:42:21 +1000
Hi there,
On 06/05/2007, at 3:34 AM, Guido Neitzer wrote:
On 05.05.2007, at 11:26, Alexander Spohr wrote:
If you don’t want to kill it the hard way, implement a
directAction to call application.terminate();
Secure it with a password and set the app to autorecover.
This doesn't necessarily help when the application is locked up
(session store or EOF deadlock). And for what other reason should
an application be manually restarted?
Perhaps the client Thierry was referring to are involved in
customising components or resources. If caching is on and they've
uploaded an adjustment to one of these, they might like to be able to
see the change immediately... But there's certainly better ways of
dealing with that.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden