edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Threads
Date: Fri, 5 Dec 2014 22:05:15 +0000	[thread overview]
Message-ID: <20141205220515.GL14122@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20141105161636.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

On Fri, Dec 05, 2014 at 04:16:36PM -0500, Karl Dahlke wrote:
> I think a seg fault in any thread brings down the entire process -
> so perhaps leaning a little towards separate processes,
> if we do separate functionality.

Indeed, that was my thinking. Although threads are lighter in terms of overhead, they also don't provide the isolation and flexibility we need.

> Can still use ipc, in its various forms, for communication,
> even common memory for global or session variables,
> though I don't know how well ipc ports to windows.

I'm not sure about portability either (see earlier emails)
but for the minute I've done some work with this stuff on Linux before and have
a few ideas how we could put things together.

> Sure, processes are less efficient than threds,
> but we're not doing a number crunching simulation here.

Yeah, and as stated above, we get more flexibility with processes.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-12-05 22:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 21:16 Karl Dahlke
2014-12-05 22:05 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-27  7:19 [edbrowse-dev] Threads Karl Dahlke
2019-08-28  1:30 ` Geoff McLane
2019-08-28  1:48   ` Karl Dahlke
2019-08-28  3:51     ` Kevin Carhart
2019-08-28  4:16       ` Karl Dahlke
2014-12-05 19:29 [Edbrowse-dev] Threads Karl Dahlke
2014-12-05 20:32 ` Adam Thompson
2014-03-21 22:56 [Edbrowse-dev] threads Karl Dahlke
2014-03-22 21:30 ` 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=20141205220515.GL14122@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).