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] protocol handlers and outputting to buffer
Date: Sat, 27 Jan 2018 09:58:59 +0000	[thread overview]
Message-ID: <20180127095859.g6tyuiuwuqu7cbao@toaster> (raw)
In-Reply-To: <20180026131346.eklhad@comcast.net>

On Fri, Jan 26, 2018 at 01:13:46PM -0500, Karl Dahlke wrote:
> Yes that sounds like a good idea.
> Go for it if you have the time, but be careful, httpConnect() is a bit of a house of cards, and I apologize for that.
> Also none of that stuff is in jsrt so you might want to retest some of the existing plugins and connectors to make sure they all still work;
> and I'll do the same once you have pushed.

Thanks, I'll have a go at it.  It'll be good to get back into the edbrowse code rather than just using it.

Any idea how I can hook plugins up to use the rest of the edbrowse browsing mechanism (not massively required but could be useful once we get protocol handlers that can download into the buffers)?

Cheers,
Adam.

  reply	other threads:[~2018-01-27  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 18:01 Adam Thompson
2018-01-26 18:13 ` Karl Dahlke
2018-01-27  9:58   ` Adam Thompson [this message]
2018-01-27 14:40     ` Karl Dahlke
2018-02-01 19:58       ` Adam Thompson
2018-02-01 20:28         ` Karl Dahlke
2018-02-09 18:44           ` Adam Thompson
2018-02-09 20:10             ` Karl Dahlke
2018-02-11 16:41               ` Adam Thompson
2018-02-11 16:54                 ` Karl Dahlke
2018-02-11 17:14                   ` Adam Thompson
2018-02-11 17:40                     ` Karl Dahlke

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=20180127095859.g6tyuiuwuqu7cbao@toaster \
    --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).