> certainly about the suggested "thread safe" design. The two threads would run separately in time, logically, because the protocol is the same, one thread is always waiting for a message from the other. Just as the two processes are essentially serialized. They never really run in parallel. Both threads will not run httpConnect at the same time, for example, it just won't happen. So I'm not too worried about threadsafe nightmares.
Still, we can keep the processes separate for a while as we think through the various implications. No problem. Only step so far is making one image, which gives us, when making xhr or whatever, all the power of edbrowse. Call httpConnect and you'll have the network of proxies and certificates, the cookies in the cookie jar, etc. > I'm now regularly seeing edbrowse-js seg faults again, Well if you have a website ... would love to track this down. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
