S
Sin Jeong-hun
Some of my clients (but I don't) get the "The underlying connection
was closed" exception. According to this article (http://
www.dotnetspider.com/resources/2596-e-underlying-connection-was-closed-A-connection.aspx)
, it's a bug of .NET 2.0.
Should I wait till Microsoft fixes it or should I use
"request.KeepAlive=false" instead, like the article suggests (despite
performance degradation)?
was closed" exception. According to this article (http://
www.dotnetspider.com/resources/2596-e-underlying-connection-was-closed-A-connection.aspx)
, it's a bug of .NET 2.0.
Should I wait till Microsoft fixes it or should I use
"request.KeepAlive=false" instead, like the article suggests (despite
performance degradation)?