edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  Threads
Date: Fri, 05 Dec 2014 16:16:36 -0500	[thread overview]
Message-ID: <20141105161636.eklhad@comcast.net> (raw)

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.
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.
Sure, processes are less efficient than threds,
but we're not doing a number crunching simulation here.

Karl Dahlke

             reply	other threads:[~2014-12-05 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 21:16 Karl Dahlke [this message]
2014-12-05 22:05 ` Adam Thompson
  -- 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=20141105161636.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).