I'm trying to make a simple little asynchronous socket server. It accepts
connections, reads and writes, but I can't make it gracefully stop listening.
listener.listen(1)
listener.beginaccept(...)
If before anyone has attempted to connect, I try to stop the listener
socket, I get nasty errors, which I can trap, but it is not obvious that it
has actually stopped or that the asynchronous callback system has been
aborted. This should be trivial. What am I missing?
Markus Stoeger - 29 Jun 2006 22:26 GMT
> I'm trying to make a simple little asynchronous socket server. It accepts
> connections, reads and writes, but I can't make it gracefully stop listening.
[quoted text clipped - 6 lines]
> has actually stopped or that the asynchronous callback system has been
> aborted. This should be trivial. What am I missing?
I dont know of another way than to call socket.Close() and catch the
resulting ObjectDisposedException on EndAccept.
hth,
Max
Jared Parsons [MSFT] - 30 Jun 2006 02:41 GMT
Hello rossu,
> I'm trying to make a simple little asynchronous socket server. It
> accepts connections, reads and writes, but I can't make it gracefully
[quoted text clipped - 6 lines]
> that it has actually stopped or that the asynchronous callback system
> has been aborted. This should be trivial. What am I missing?
How are you stopping the Socket?
--
Jared Parsons [MSFT]
jaredpar@online.microsoft.com
All opinions are my own. All content is provided "AS IS" with no warranties,
and confers no rights.
rossu - 30 Jun 2006 20:33 GMT
listener.close
> Hello rossu,
>
[quoted text clipped - 16 lines]
> All opinions are my own. All content is provided "AS IS" with no warranties,
> and confers no rights.
Jared Parsons [MSFT] - 30 Jun 2006 22:03 GMT
Hello rossu,
> listener.close
It seems like the option you're looking for here is a way to essentially
cancel the BeginAccept() call. Unfortunately that is not implemented for
the IAsyncResult pattern.
You're best option is to differentiate based on the exception when you call
EndAccept. If it's an ObjectDisposed exception that means that you called
Close on the listener socket someplace else. Otherwise there was a general
issue when someone attempted to connect to the socket.
--
Jared Parsons [MSFT]
jaredpar@online.microsoft.com
All opinions are my own. All content is provided "AS IS" with no warranties,
and confers no rights.