From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] One program Two processes
Date: Wed, 23 Dec 2015 14:07:46 -0500 [thread overview]
Message-ID: <20151123140746.eklhad@comcast.net> (raw)
In-Reply-To: <20151223184500.GB2992@hob.adamthompson.me.uk>
> 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
next prev parent reply other threads:[~2015-12-23 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 15:09 Karl Dahlke
2015-12-23 18:45 ` Adam Thompson
2015-12-23 19:07 ` Karl Dahlke [this message]
2015-12-23 19:59 ` Chris Brannon
2015-12-23 20:44 ` Karl Dahlke
2015-12-24 11:19 ` Adam Thompson
2015-12-24 13:15 ` Karl Dahlke
2015-12-24 18:39 ` Adam Thompson
2015-12-25 2:29 ` Karl Dahlke
2015-12-25 23:18 ` Adam Thompson
2015-12-25 23:51 ` Karl Dahlke
2015-12-26 9:11 ` Adam Thompson
2015-12-26 13:36 ` Karl Dahlke
2015-12-26 15:10 ` Adam Thompson
2015-12-26 15:23 ` Karl Dahlke
2015-12-26 15:40 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151123140746.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).