From: Lars Ingebrigtsen <larsi@gnus.org>
To: 22493@debbugs.gnu.org
Subject: bug#22493: 25.1.50; open-gnutls-stream doesn't respect :nowait, so the connections are synchronous
Date: Sun, 31 Jan 2016 02:10:04 +0100 [thread overview]
Message-ID: <87vb6ay2oj.fsf@gnus.org> (raw)
In-Reply-To: <878u36fung.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 31 Jan 2016 01:40:51 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So that has to be rewritten. But I'm not sure how... We, like, have
> several layers of possible sentinels here, and... uhm...
gnutls-negotiate (in Lisp) is basically a shim over gnutls-boot (in C).
It computes some parameters that are passed in as an keyword list to
gnutls-boot.
So: gnutls.el could be refactored to have a function that computes that
stuff, and then gnutls-mark-process could take that keyword list and
stash it in the process object. connect_network_socket could then (in
:nowait mode) call gnutls-boot directly, keeping it all nice and safe in
the C layer.
That would obviate the sentinel, and make this all transparent for the
caller.
I think.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-01-31 1:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 4:00 bug#22493: 25.1.50; open-gnutls-stream doesn't respect :nowait, so the connections are synchronous Lars Ingebrigtsen
2016-01-30 4:45 ` Lars Ingebrigtsen
2016-01-30 9:21 ` Eli Zaretskii
2016-01-30 22:55 ` Lars Ingebrigtsen
2016-01-31 0:40 ` Lars Ingebrigtsen
2016-01-31 1:10 ` Lars Ingebrigtsen [this message]
2016-01-31 16:00 ` Eli Zaretskii
2016-01-31 15:59 ` Eli Zaretskii
2016-01-31 23:17 ` Lars Ingebrigtsen
2016-02-01 2:41 ` Lars Ingebrigtsen
2016-02-01 3:41 ` Eli Zaretskii
2016-02-01 4:01 ` Lars Ingebrigtsen
2016-02-01 18:50 ` Eli Zaretskii
2016-02-02 1:43 ` Lars Ingebrigtsen
2016-02-02 16:10 ` Eli Zaretskii
2016-02-03 1:10 ` Lars Ingebrigtsen
2016-02-03 1:58 ` Lars Ingebrigtsen
2016-02-03 15:52 ` Eli Zaretskii
2016-02-04 2:47 ` Lars Ingebrigtsen
2016-02-04 16:39 ` Eli Zaretskii
2016-02-05 2:36 ` Lars Ingebrigtsen
2016-02-05 7:24 ` Eli Zaretskii
2016-02-05 7:34 ` Lars Ingebrigtsen
2016-02-05 9:18 ` Eli Zaretskii
2016-02-06 3:03 ` Lars Ingebrigtsen
2016-02-06 7:51 ` Eli Zaretskii
2016-02-06 7:57 ` Lars Ingebrigtsen
2016-02-03 15:51 ` Eli Zaretskii
2016-02-04 2:59 ` Lars Ingebrigtsen
2016-01-31 15:57 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb6ay2oj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22493@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).