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: Sun, 11 Feb 2018 16:41:42 +0000	[thread overview]
Message-ID: <20180211164142.x5wa46v7wuzz7dmp@toaster> (raw)
In-Reply-To: <20180109151024.eklhad@comcast.net>

On Fri, Feb 09, 2018 at 03:10:24PM -0500, Karl Dahlke wrote:
> curl has gopher support.
> Tell edbrowse to use curl to download anything gopher, just as it downloads http or https.
> Look at http.c line 937, perhaps we can just add gopher to the disjunction.
> Perhaps headers will come across, like http headers, with content type, and of course the file could have suffixes.
> I'd play around with it but don't have a gopher server with various files to test.
> Unless there is a public one.
> Just change that one line and run with db4 and see what kind of headers come across.

Yeah I know, I was contemplating patching the support directly into edbrowse but wasn't sure which would be
easier plus it'd be good if plugins could more closely integrate with the rest of edbrowse in any case.

On the subject of gopher specifically it has no headers, the content type is done in the selector.  It also has a menu which needs to be parsed (basically a list of selectors and text).  Quite simple but would need the
rendering code to be aware of it somehow.
I'm not sure if I could do something like the ftp code?

Anyway, sdf.org (and sdf-eu.org) run a gopher server, and there're a bunch more (including a project
gutenberg one but I'm not sure how standard that one is).

Cheers,
Adam.

  reply	other threads:[~2018-02-11 16:41 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
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 [this message]
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=20180211164142.x5wa46v7wuzz7dmp@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).