[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Demanding Interoperability to Strengthen the Free (Libre) Web: Intro

From: Vivien Kraus
Subject: Re: Demanding Interoperability to Strengthen the Free (Libre) Web: Introducing DISFLUID
Date: Mon, 02 Aug 2021 10:20:24 +0200
User-agent: Evolution 3.34.2

Hello Aleix !

Le dimanche 01 août 2021 à 23:27 -0700, Aleix Conchillo Flaqué a
écrit :
> Unfortunately guile-json doesn't follow srfi-180 api (it was created
> much sooner), but regarding alists' keys it can support both symbols
> and strings. So you can do (scm->json '((foo . "bar"))) or (scm->json 
> '(("foo" . "bar"))) and both would work the same.

Exactly! The problem is in the other way around, json->scm. By default,
I get stringly-keyed objects, so I add another pass to convert them to
symbolicly-keyed objects.

> By the way, a long time ago I also worked on guile-jwt (
> which is SUPER basic
> compared to what you've done. I was planning to add JWK support at
> some point. I'm wondering if we could take your code and merge it
> into guile-jwt so other projects can use it. What do you think? Right
> now I don't have much time but if you say it's fine I could work on
> it whenever I'm free.

That would be awesome, but working with C bindings is a pain with
guile. If you inherit all the JWS and JWK code, I still need to keep
them around for things like hashing the URIs for the cache and resource
server and generating random numbers. The clever thing to do would be
to switch to guile-gcrypt first (so that I don’t have any more C) and
then move the code to guile-jwt (we can still change the API if you
prefer another one, I don’t have a 1.0 release yet).

Since that code will most likely be run on web servers, have you
considered releasing it under the AGPL?

Best regards,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]