I wonder if I handle a socket in a dll, is it going to be slower than if I handle it at the application itself? Thanks.
Printable View
I wonder if I handle a socket in a dll, is it going to be slower than if I handle it at the application itself? Thanks.
DLLs are mapped into each application's memory space, so unless you are contemplating something unusual (like the /DELAYLOAD switch), I can't think of any reason that it might be slower.
Note that Winsock is itself a DLL, and is mapped into the application's memory space when the application calls WSAStartup().
Mike
Thanks.