I've been playing around with the winsock control off and on for a while now, and I'm trying to make a server side app capable of handling multiple tcp connections. What is the best way to get around the single threading nature of VB?
An out of process ActiveX exe was my first thought, with a single winsock control listening in the app and passing on requestID's. The problem is that to instance and then destroy the exe dynamically when a connection comes in is going to be really slow. What's the best way to do this?

Thanks