From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] mbox improvements
Date: Sun, 15 May 2016 23:59:30 +0000 [thread overview]
Message-ID: <20160515235932.18313-1-e@80x24.org> (raw)
1/1 is obvious and should help with caching/mirroring, though
we could also make the gzip header itself consistent.
2/2 is an interesting use of Danga::Socket::write callbacks.
I'm still evaluating different ways to make gigantic responses
saner and I'm not sure if I like the way this is currently
done; but for now it works.
lib/PublicInbox/Mbox.pm | 83 ++++++++++++++++++++++++++++++++++++++++++++-----
lib/PublicInbox/WWW.pm | 11 +++++++
2 files changed, 86 insertions(+), 8 deletions(-)
next reply other threads:[~2016-05-15 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 23:59 Eric Wong [this message]
2016-05-15 23:59 ` [PATCH 1/2] mbox: consistent header order when decompressed Eric Wong
2016-05-15 23:59 ` [PATCH 2/2] mbox: support /$INBOX/all.mbox.gz endpoint 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=20160515235932.18313-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).