W
WTH
with a C# client (and/or server, but server not important)?
I've got a scalable high speed (uses completion ports) C++ TCP/IP
communication server but I'd like to write a C# client that other C# devs at
our company can just drop in and use (it's an event and message passing
system.)
I'm sure, as most things C#/.Net, it's relatively simple, but if I can
discover some caveats the easy way rather than the hard way I'm always up
for that .
Technical minutae: The client must be able to transmit and receive
simultaneously (asynchronous) and ideally (but not necessarily) I'd like to
be able to share the socket amongst threads (like you can do with a raw
socket but not an MFC socket.)
Thanks,
WTH
I've got a scalable high speed (uses completion ports) C++ TCP/IP
communication server but I'd like to write a C# client that other C# devs at
our company can just drop in and use (it's an event and message passing
system.)
I'm sure, as most things C#/.Net, it's relatively simple, but if I can
discover some caveats the easy way rather than the hard way I'm always up
for that .
Technical minutae: The client must be able to transmit and receive
simultaneously (asynchronous) and ideally (but not necessarily) I'd like to
be able to share the socket amongst threads (like you can do with a raw
socket but not an MFC socket.)
Thanks,
WTH