> I'm also going to look into IPC mechanisms for Windows Geoff says that if you want portable flexible interprocess communication, (more flexible than pipes), you have to bite the bullet and use sockets. Processes listen on certain ports, send messages to each other via tcp, using send() and recv(), which are both unix and windows calls. It's rather a pain to set up initially but when it is rolling it works fine. I'm not looking forward to that, but as I think about itI'm more convinced he's right, and why should I have to think about it at all; he's the expert. He knows.
So we may have to bring back tcp.c from the archives of git. This was a wrapper file that set up sockets in a unix / windows hiding fashion, with one common interface. We used it long before curl, when I did it all by hand, then through it away since curl seems to do everything. But here we may need it again so Chris you might want to at least find the latest and clean it up etc. There was also a tcp.h but honestly it was small and I wouldn't mind folding it into eb.h. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
