unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 70645@debbugs.gnu.org
Subject: bug#70645: Reliable HTTPS networking
Date: Mon, 29 Apr 2024 11:51:36 +0100	[thread overview]
Message-ID: <875xw01lxj.fsf@cbaines.net> (raw)

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

For years now I've been trying to work out how to do reliable HTTPS
networking with Guile, where reliable just means that it can't hang
indefinitely.

After a few wrong turns, I believe the way to do this is use
non-blocking ports as that combined with suspendable ports in Guile
allows you to provide current-read-waiter/current-write-waiter
procedures that will timeout at some point.

I think the final hurdle is to get tls-wrap in (web client) to support
Asynchronous operation with GnuTLS [1] and I think there are only a
couple of things missing. make-session needs passing
connection-flag/nonblock and error/again plus error/interrupted
exceptions need handling for the handshake using the information from
record-get-direction about whether Guile should wait to write or read.

1: https://gnutls.org/manual/html_node/Asynchronous-operation.html

I think I forgot to move things forward after guile-gnutls 4.0.0
released with record-get-direction, so I'm opening this bug to try and
keep track of things.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

             reply	other threads:[~2024-04-29 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 10:51 Christopher Baines [this message]
2024-04-29 11:57 ` bug#70645: [PATCH 1/2] Allow specifying the socket style for open-socket-for-uri Christopher Baines
2024-04-29 11:57   ` bug#70645: [PATCH 2/2] web: Handle non-blocking ports in tls-wrap Christopher Baines
2024-04-29 12:05 ` bug#70645: Reliable HTTPS networking Christopher Baines

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xw01lxj.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=70645@debbugs.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).