From: Ricardo Wurmus <rekado@elephly.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26940@debbugs.gnu.org
Subject: bug#26940: [PATCH 1/3] gnu: Add http-parser.
Date: Mon, 15 May 2017 21:26:09 +0200 [thread overview]
Message-ID: <87efvp7wha.fsf@elephly.net> (raw)
In-Reply-To: <87inl2dnlg.fsf@fastmail.com>
Marius Bakke <mbakke@fastmail.com> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> * gnu/packages/web.scm (http-parser): New variable.
>
> [...]
>
>> + (description "This is a parser for HTTP messages written in C. It parses
>> +both requests and responses. The parser is designed to be used in performance
>> +HTTP applications. It does not make any syscalls nor allocations, it does not
>> +buffer data, it can be interrupted at anytime. Depending on your architecture,
>> +it only requires about 40 bytes of data per message stream (in a web server
>> +that is per connection).")
>
> Some missing spaces in the description here. The sentences also read a
> bit weird, should it be "high-performance HTTP applications"? Or
> performant? Maybe just "fast"? LGTM with cosmetic fix.
Thanks for the suggestions!
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-05-15 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 13:58 bug#26940: Add SSSD Ricardo Wurmus
2017-05-15 14:01 ` bug#26940: [PATCH 1/3] gnu: Add http-parser Ricardo Wurmus
2017-05-15 14:01 ` bug#26940: [PATCH 2/3] gnu: Add ding-libs Ricardo Wurmus
2017-05-15 17:43 ` Marius Bakke
2017-05-15 14:01 ` bug#26940: [PATCH 3/3] gnu: Add sssd Ricardo Wurmus
2017-05-15 17:44 ` Marius Bakke
2017-05-15 19:33 ` Ricardo Wurmus
2017-05-15 20:33 ` Leo Famulari
2017-05-15 20:42 ` Mathieu Othacehe
2017-05-15 21:00 ` Ricardo Wurmus
2017-05-15 17:41 ` bug#26940: [PATCH 1/3] gnu: Add http-parser Marius Bakke
2017-05-15 19:26 ` Ricardo Wurmus [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efvp7wha.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=26940@debbugs.gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).