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] protocol handlers and outputting to buffer
Date: Sun, 11 Feb 2018 12:40:59 -0500	[thread overview]
Message-ID: <20180111124059.eklhad@comcast.net> (raw)
In-Reply-To: <20180211171402.vsqhyaogn7djvawl@toaster>

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

http.c  ftpConnect() and parse_directory_listing().
You might need gopher analogies for these two functions.
Obviously you'd rename the second to parse_ftp_directory() or some such, then make a gopher version.
Seems doable.
Some of the complexity of ftpConnect is that we can download, or even download in background, probably this carries over into gopher, don't see why it wouldn't or shouldn't.

I will look into the speed issue, and/or infinite loop, obviously edbrowse is still somewhat unusable.
Remember there are sites like nasa that you can't even browse without js.
My push for getComputedStyle will make a lot of sites run faster.
Yes, stackoverflow does get lost, but not in css, it's some other js that is brought in.

Karl Dahlke

      reply	other threads:[~2018-02-11 17:40 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
2018-02-11 16:54                 ` Karl Dahlke
2018-02-11 17:14                   ` Adam Thompson
2018-02-11 17:40                     ` Karl Dahlke [this message]

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=20180111124059.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).