I know about domain sockets, but heard they were not available on windows. If they were then we could create various /tmp/.edbrowse/sockets and bounce through those. If not then we use ports as usual.
Perhaps your security concerns are an argument in favor of passing the internet data back from edbrowse-curl to edbrowse via temp files, created 0600 for the user. These temp files could not be "sniffed". Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
