From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: ‘http-get*’ and all that
Date: Sat, 12 Jan 2013 00:30:33 +0100 [thread overview]
Message-ID: <8762331ena.fsf@gnu.org> (raw)
In-Reply-To: <87bocvzha2.fsf@pobox.com> (Andy Wingo's message of "Fri, 11 Jan 2013 19:49:41 +0100")
Howdy!
Andy Wingo <wingo@pobox.com> skribis:
> On Fri 11 Jan 2013 17:53, ludo@gnu.org (Ludovic Courtès) writes:
>
>> "Andy Wingo" <wingo@pobox.com> skribis:
>>
>>> (http-get): Redefine in terms of http-get. Deprecate the
>>> #:extra-headers argument in favor of #:headers. Allow a body. Add a
>>> #:streaming? argument, subsuming the functionality of http-get*.
>>> (http-get*): Deprecate.
>>
>> ‘http-get*’ was added in 2.0.7, so it doesn’t seem wise to deprecate it
>> just a couple of months later, no?
>
> In many ways it's better to deprecate early while there are few users,
> and the change was recent. It's not like the interfaces are actually
> going away for a while.
Right. It still gives a bad impression, I think, but it’s technically
manageable.
>> As for adding another keyword instead of another procedure, that’s fine,
>> but not strikingly more elegant either, IMO.
>
> We would have had to add 3 or 4 additional procedures: http-put*,
> http-post*, etc. It was actually less work to add #:streaming? to
> http-get, and at that point http-get* is superfluous.
OK, I see. Uniformity among http-{post,put,get} is probably a good idea.
> When making these choices, I used Python's "requests" module as a guide:
> http://docs.python-requests.org/en/latest/ It's actually quite nice to
> use.
Interesting (I admit this is not part of my culture ;-)).
>> In terms of process, I’d prefer more discussion. For instance, while we
>> briefly discussed (ice-9 iconv) on IRC, posting an RFC here, or at least
>> a note, would have helped give the feeling that people are in the loop,
>> and may have turned up useful feedback.
>
> Sure, no problem. I had assumed that the old guile-user discussion was
> sufficient (http://thread.gmane.org/gmane.lisp.guile.user/9373), but I
> can't blame you for forgetting about a thread last April ;)
Oh, I confess I had forgotten about that one, sorry.
> Any other points on the code?
No! :-)
Ludo’.
next prev parent reply other threads:[~2013-01-11 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TtfmM-0002TY-7q@vcs.savannah.gnu.org>
2013-01-11 16:53 ` ‘http-get*’ and all that Ludovic Courtès
2013-01-11 18:49 ` Andy Wingo
2013-01-11 23:30 ` Ludovic Courtès [this message]
2013-01-12 4:09 ` Daniel Hartwig
2013-01-21 21:15 ` Andy Wingo
2013-01-11 17:15 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.7-25-g990b11c Ludovic Courtès
2013-01-11 20:28 ` Andy Wingo
2013-01-11 23:39 ` Ludovic Courtès
2013-01-12 15:17 ` Mark H Weaver
2013-01-12 20:34 ` 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=8762331ena.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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.
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).