Karl Dahlke <[email protected]> writes: > but if we spin up one curl server per user, > it has to listen on a per-user edbrowse port, > so that's a bit more complicated.
Yes, it's terribly complicated, and this is just the sort of scenario for which Unix-domain sockets were designed. I'd say use Unix domain sockets on Unix and Mac, and IP sockets with loopback on Windows, unless there's an implementation of Unix domain sockets for Windows. In any case, we only care about the socket type when it is created and bound or connected. I.E., the socket(), bind(), and connect() calls. So most of the time nobody needs to care whether it is an IP socket or a Unix domain socket. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
