From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 30154@debbugs.gnu.org
Subject: bug#30154: [PATCH] web: Add http-patch.
Date: Mon, 18 Jun 2018 14:13:27 +0200 [thread overview]
Message-ID: <87po0ouwbc.fsf@gnu.org> (raw)
In-Reply-To: <cu7r2q9cbda.fsf@systemreboot.net> (Arun Isaac's message of "Mon, 29 Jan 2018 14:03:53 +0530")
Hello,
Arun Isaac <arunisaac@systemreboot.net> skribis:
> Mark H Weaver <mhw@netris.org> writes:
>
>>> If you think it's not a good idea to include http-patch in guile, maybe
>>> we can export define-http-verb and/or request so that it is easy for
>>> users to create their own custom HTTP methods. WDYT?
>>
>> I would prefer to export the 'request' procedure from (web client),
>> although it should probably be exported as a different name, maybe
>> 'http-request'. Would that work for you?
>
> Yes, exporting 'request' alone would serve my purpose, although
> 'define-http-verb' would make my script much shorter. But, I'll leave it
> to your judgement. Should I send a new patch exporting 'request' alone?
Could you do that? The ‘request’ procedure can simply be made public
and otherwise left unchanged, but we’d need a docstring and an entry in
the manual. Can you take a look?
I’ll happily apply the patch afterwards, and I promise you won’t have to
wait as much as you did so far! :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-06-18 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 9:43 bug#30154: [PATCH] web: Add http-patch Arun Isaac
2018-01-26 23:22 ` Mark H Weaver
2018-01-28 0:27 ` Arun Isaac
2018-01-28 21:10 ` Mark H Weaver
2018-01-29 8:33 ` Arun Isaac
2018-06-18 12:13 ` Ludovic Courtès [this message]
2018-06-19 5:34 ` Arun Isaac
2018-06-21 17:27 ` bug#30154: [PATCH] web: Export http-request Arun Isaac
2018-06-23 21:31 ` Ludovic Courtès
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=87po0ouwbc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30154@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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).