VB.Net, TCPListener.Accept() not blocking?

TCPListener.Accept() not blocking?

Author	Message
Ben Vanik - 37613 #1 / 5	TCPListener.Accept() not blocking? After looking through MSDN and the gotdotnet dateTimeServer sample, I spun out a little net app. Well, to my suprise I started getting errors right away. After about 5 minutes I realized my .Accept function on the listening class was not blocking! I found a way around it (simply call .Pending to see if there are any waiting connections, then do the Accept), but I'm curious as to why this isn't document, and actually described as the opposite. Ex: ' Accept will block until someone connects Dim s As Socket = tcpl.Accept() Nope, just returns Nothing! Am I just doing something wrong? Ben Vanik
Thu, 29 May 2003 06:55:13 GMT

Rockford Lhotk #2 / 5	TCPListener.Accept() not blocking? Perhaps it is a bug in the default behavior. I am using code which explicitly turns blocking on and Accept seems to block just fine. The docs say blocking is the default, but maybe not - I didn't check that... -- Rockford Lhotka Quote: > After looking through MSDN and the gotdotnet dateTimeServer sample, I spun > out a little net app. Well, to my suprise I started getting errors right > away. After about 5 minutes I realized my .Accept function on the listening > class was not blocking! I found a way around it (simply call .Pending to see > if there are any waiting connections, then do the Accept), but I'm curious > as to why this isn't document, and actually described as the opposite. > Ex: > ' Accept will block until someone connects > Dim s As Socket = tcpl.Accept() > Nope, just returns Nothing! > Am I just doing something wrong? > Ben Vanik
Fri, 30 May 2003 14:07:57 GMT

Ben Vani #3 / 5	TCPListener.Accept() not blocking? Thanx Yes, I believe, contrary to the docs, that blocking is NOT on by default weird.... typical MS :) Ben Vanik Quote: > Perhaps it is a bug in the default behavior. I am using code which > explicitly turns blocking on and Accept seems to block just fine. The docs > say blocking is the default, but maybe not - I didn't check that... > -- > Rockford Lhotka > > After looking through MSDN and the gotdotnet dateTimeServer sample, I spun > > out a little net app. Well, to my suprise I started getting errors right > > away. After about 5 minutes I realized my .Accept function on the > listening > > class was not blocking! I found a way around it (simply call .Pending to > see > > if there are any waiting connections, then do the Accept), but I'm curious > > as to why this isn't document, and actually described as the opposite. > > Ex: > > ' Accept will block until someone connects > > Dim s As Socket = tcpl.Accept() > > Nope, just returns Nothing! > > Am I just doing something wrong? > > Ben Vanik
Fri, 30 May 2003 19:48:10 GMT

Jonathan Alle #4 / 5	TCPListener.Accept() not blocking? The default for Sockets is Blocking=False. -- Jonathan Allen Quote: > Thanx > Yes, I believe, contrary to the docs, that blocking is NOT on by default > weird.... typical MS :) > Ben Vanik > > Perhaps it is a bug in the default behavior. I am using code which > > explicitly turns blocking on and Accept seems to block just fine. The docs > > say blocking is the default, but maybe not - I didn't check that... > > -- > > Rockford Lhotka > > > After looking through MSDN and the gotdotnet dateTimeServer sample, I > spun > > > out a little net app. Well, to my suprise I started getting errors right > > > away. After about 5 minutes I realized my .Accept function on the > > listening > > > class was not blocking! I found a way around it (simply call .Pending to > > see > > > if there are any waiting connections, then do the Accept), but I'm > curious > > > as to why this isn't document, and actually described as the opposite. > > > Ex: > > > ' Accept will block until someone connects > > > Dim s As Socket = tcpl.Accept() > > > Nope, just returns Nothing! > > > Am I just doing something wrong? > > > Ben Vanik
Sat, 31 May 2003 01:30:00 GMT

Scott Sejk #5 / 5	TCPListener.Accept() not blocking? Rocky, Have you come across a way to detect if a connected socket has been abnormally closed/disconnected? Also, when using the BeginReceive method of a Socket object, is it normal to have to keep calling the BeginReceive method repeatedly after receiving data? Any help would be appreciated. Quote: > Perhaps it is a bug in the default behavior. I am using code which > explicitly turns blocking on and Accept seems to block just fine. The docs > say blocking is the default, but maybe not - I didn't check that... > -- > Rockford Lhotka > > After looking through MSDN and the gotdotnet dateTimeServer sample, I spun > > out a little net app. Well, to my suprise I started getting errors right > > away. After about 5 minutes I realized my .Accept function on the > listening > > class was not blocking! I found a way around it (simply call .Pending to > see > > if there are any waiting connections, then do the Accept), but I'm curious > > as to why this isn't document, and actually described as the opposite. > > Ex: > > ' Accept will block until someone connects > > Dim s As Socket = tcpl.Accept() > > Nope, just returns Nothing! > > Am I just doing something wrong? > > Ben Vanik
Fri, 06 Jun 2003 23:04:51 GMT

Page 1 of 1

[ 5 post ]