edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: ubuntu@geoffair.info
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] socket.c and socket.h
Date: Thu, 31 Dec 2015 09:54:46 -0500	[thread overview]
Message-ID: <20151131095446.eklhad@comcast.net> (raw)
In-Reply-To: <CA+Pgot+=bbdLr6GUo7++a9LRUGCG9uAHqicMcx97zq8DH-Rvrg@mail.gmail.com>

Hi Geoff,

I am so sorry we left you out of the loop. My fault.

For ease of distribution and other reasons,
we're trying to have one executable image that does different things
under different names.
There's lots of this in unix.
Example /bin/awk symlinked to /bin/gawk,
same program having so much overlap,
but does some slightly different things depending on argv[0],
on how it's called, whether awk or gawk.
Same for /bin/bash and /bin/sh, etc.
So we want edbrowse and edbrowse-js, but the same image,
the former still invoking the latter just like you have it.
I'm not sure the best approach here for windows,
feel free to edit cmakelists if there's any better way.

We may also have edbrowse-curl, again the same image but doing different things,
maybe others in the future.

Glad to hear sockets still works after 15 years,
though we may add udp, which was never there before.
This has some advantages for many to many communications,
many threads in this process to many threads in that one,
whereas both pipes and sockets are very much point to point.

I'll write more in a bit, and will be sure to cc you
when something is relevant.
Hope you have a great new year.

Karl Dahlke

  parent reply	other threads:[~2015-12-31 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30  2:46 Karl Dahlke
     [not found] ` <CA+Pgot+=bbdLr6GUo7++a9LRUGCG9uAHqicMcx97zq8DH-Rvrg@mail.gmail.com>
2015-12-31 14:54   ` Karl Dahlke [this message]
2016-01-01  2:10     ` [Edbrowse-dev] telling JS about allowXHR Kevin Carhart
2016-01-01  2:43       ` Karl Dahlke
2016-01-01  4:18         ` Kevin Carhart

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=20151131095446.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=ubuntu@geoffair.info \
    /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).