From: Ricardo Wurmus <rekado@elephly.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [EXT] Guile AWS
Date: Mon, 12 Apr 2021 18:19:13 +0200 [thread overview]
Message-ID: <87lf9nv5ku.fsf@elephly.net> (raw)
In-Reply-To: <CAJ=RwfZTHeMq6g3-qSp4MRDexd0YKQOpQqo1V89g_ov6DZ-9Mw@mail.gmail.com>
Thompson, David <dthompson2@worcester.edu> writes:
> Years ago I took the same approach to generate a Guile API for
> CloudFormation (an unreleased experiment) and was hoping that someone
> would do the same for the entire AWS API.
Your CloudFormation experiment was indeed the spark that ignited the
fire. Guile AWS isn’t based on your code, but I learned a lot from
looking at it a few years back, and it planted the seed to implement
Guile AWS using the same approach.
> As far as error handling goes, the official AWS SDK for NodeJS may be
> something to study. It uses asyncs (which is a syntax over simple
> promises) to allow for threading together multiple API requests
> together and handle errors without too much headache. Most of the time
> I use the Ruby SDK, less often the Python SDK (boto3), and in both you
> just have to catch exceptions or inspect responses yourself, so if
> that's what you have to do with the guile-aws for the time being then
> you're still on par with several official SDKs. Those SDKs don't do
> anything magical with the responses, either, so I consider being given
> a big ol' deserialized json/xml response in the form of a compound
> s-exp to be just fine.
Ah, that’s good to know. Still, I think at the very least guile-aws
ought to present a unified data structure — either an alist, a JSON
expression, or some SXML, but not a different structure dependent on
whatever the API uses internally.
--
Ricardo
prev parent reply other threads:[~2021-04-12 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:47 Guile AWS Ricardo Wurmus
2021-04-12 16:02 ` [EXT] " Thompson, David
2021-04-12 16:19 ` 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://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=87lf9nv5ku.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=dthompson2@worcester.edu \
--cc=guile-user@gnu.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).