Re: Stopping a DO work
Re: Stopping a DO work
- Subject: Re: Stopping a DO work
- From: Peter Sichel <email@hidden>
- Date: Sun, 23 Sep 2001 08:03:46 -0400
I've done this by having the server thread call back
into the main thread periodically to check for "UserDidAbort".
In my case, the server thread might be sleeping waiting for
kernel I/O (networking), so having it wake periodically to
check for user abort is a common unix design.
If the server fails to respond, we can still kill the thread
or interrupt it.
- Peter
At 11:47 AM +0200 9/23/01, kubernan wrote:
Hello,
I have a client/server application based on DO.
After sending a request to the server, the response
can take very long time. It depends on some paramaters
on my client GUI.
What i want to do is to offer to the user the possibility
to stop the server work (not the server itself).
The setReplyTimeout (NSConnection) doesn't stop the
server process but only that wait of the client.
What is the mean to stop a DO server process ?
Thx.
Kub.
--