From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] http: start migrating to pull-based I/O
Date: Sat, 21 May 2016 03:03:15 +0000 [thread overview]
Message-ID: <20160521030317.24152-1-e@80x24.org> (raw)
There'll be more conversions coming, but this should decouple
some of our PSGI code from Danga::Socket internals while also
providing better backpressure handling inside PublicInbox::HTTP
to avoid excessive buffering.
Eric Wong (2):
http: reduce over-buffering for getline responses
mbox: switch generation over to pull model
lib/PublicInbox/Git.pm | 2 +
lib/PublicInbox/HTTP.pm | 26 ++++++--
lib/PublicInbox/Mbox.pm | 157 +++++++++++++++---------------------------------
3 files changed, 74 insertions(+), 111 deletions(-)
next reply other threads:[~2016-05-21 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 3:03 Eric Wong [this message]
2016-05-21 3:03 ` [PATCH 1/2] http: reduce over-buffering for getline responses Eric Wong
2016-05-21 3:03 ` [PATCH 2/2] mbox: switch generation over to pull model Eric Wong
2016-05-21 4:43 ` [PATCH 4/1] unsubscribe: prevent decrypt from showing random crap Eric Wong
2016-05-21 5:31 ` [PATCH] localize $/ in more places to avoid potential problems Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160521030317.24152-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).