> I'd imagine that any .NET socket object has more "state" than > just an OS socket handle. (There are many kinds of > sockets; listening sockets [for servers], service sockets [a > server-side socket created to service a client request], > client sockets, UDP sockets, blah blah. Even if you only > think of client-side TCP sockets, the state of the socket is > non-trivial, and having private data that represents the > state -- rather than querying the API for each state value > when needed -- makes sense.)
Yes. I realize that now that I think about it a bit more. I don't know what kind of socket it is. My best guess would be that it's a TCP network socket, but I couldn't be sure since I only can get the handle and use it in FD_SET. I managed to put all this into managed C++, so that part is working well. I'm having other issues, but that's just probably my lack of knowledge on managed C++, so off the CX list i go... thanks for the help, -akshay =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
