First time here? Check out the site's "greatest hits" or read a post from the archives. Feel free to leave a comment or ask a question, and consider subscribing to the latest posts via RSS or e-mail. Thanks for visiting!
« Ignorance, Confusion and Higgledy-Piggle... | Main | Noteable - Extending Windows NT Server 4... »

Has anyone else seen WinSock Error 10055 WSAENOBUFS when working with .NET Remoting? 

.NET is a great abstraction layer, arguably the best, but I tell ya, I spend more time with Packet Sniffers and running around at the levels of:

A. Threading
2. Sockets

than I ever used to...it feels like these two core OS areas are being stressed more now that .NET enables us to built software bigger, better, faster.  Our abstraction layer is creaking under the heavy load of either my creativity or my ignorance.



Comments are closed.

Contact

Sponsors

Hosting By

On this page...

Tags

Calendar

<January 2009>
SunMonTueWedThuFriSat
28293031123
45678910
11121314151617
18192021222324
25262728293031
1234567

Archives

Google Ads