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] Rebundle / One program # processes
Date: Sat, 26 Dec 2015 10:56:03 -0500	[thread overview]
Message-ID: <20151126105603.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1512260025000.19545@carhart.net>

> I could revise this now, but I'm inclined to wait a while, because
> it sounds like you might be about to supercede it with increments

Oh I don't know, your submissions are always helpful.
And our revisions may well be transparent to your work.
In other words, you call httpConnect() either way,
and it might call curl locally, as it does now,
or it may send a request to a curl server and give you the response,
but the function call is likely to be the same anyways.
So I'd say press on; the only question is whether we paste it in
or wait, whether it adds value as it is in its synchronous mode,
whether it accesses more websites or causes unexpected trouble, or both.
It's a judgment call.
Usually I say "put it in", but that's me.

Karl Dahlke

  reply	other threads:[~2015-12-26 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 23:13 [Edbrowse-dev] Rebundle Karl Dahlke
2015-12-23 23:17 ` Kevin Carhart
2015-12-24  0:01   ` Kevin Carhart
2015-12-24  0:04     ` Kevin Carhart
2015-12-24  0:17       ` Karl Dahlke
2015-12-24  0:46         ` Kevin Carhart
2015-12-25 15:10       ` Karl Dahlke
2015-12-26  8:44         ` [Edbrowse-dev] Rebundle / One program # processes Kevin Carhart
2015-12-26 15:56           ` Karl Dahlke [this message]
2015-12-27  7:54             ` Adam Thompson
2015-12-27  9:18               ` [Edbrowse-dev] response headers and body? Kevin Carhart
2015-12-27 13:38                 ` Karl Dahlke
2015-12-27 21:03                   ` 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=20151126105603.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).