There is no method for interfacing to a socket via a descriptor in the managed space... IE, the socket connection is already made, and my program is called with the socket descriptor on the command line, passing the use of the socket to another program.
David Anes wrote: > Hi Michael, > > Why not use System.Net.Sockets namespace? I think this is what you are > searching for. > > Regards, > David Anes. > > 2007/3/25, Michael J. Ryan < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>>: > > Is there a standard library, in linux, and/or OSX to handle the > following.. > > Two external methods... 1, send a byte array via a socket > descriptor.. 2, > receive a single byte via a descriptor? I wrote a small stub in C > to handle > this, but wasn't sure if it would be better to have a compile > setting in the > C# project itself to address to winsock on windows, and ??? on > linux... That > way another dll/so doesn't need to be compiled in the native > platform for this > tiny piece. > > I'm not really very good with the P/Invoke stuff, or even sure how > to make > such a decision, or do it at runtime... Any help would be appreciated. -- Michael J. Ryan - tracker1(at)theroughnecks(dot)com - www.theroughnecks.net icq: 4935386 - AIM/AOL: azTracker1 - Y!: azTracker1 - MSN/Win: (email) _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
