curl / Mailing Lists / curl-users / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: JSON support

From: Mac-Fly via curl-users <curl-users_at_lists.haxx.se>
Date: Thu, 20 Jan 2022 15:59:27 +0100

Hi Daniel,

I am a long-term (happy) cURL user that crafted JSON support around cURL manually for exactly the need you mentioned.
I would welcome support for JSON in cURL, it should make the life easier (although with a good JSON lib this was not really a big deal to do something around cURL).

My 2 cents from my personal experience you may want to consider:

While your article focusses on sending, you may want to also consider parsing for decision making which usually comes first (request-response).
To access values I am using two extensions: JSON Pointer and JSONPath (the latter is a more recent draft standard).
If the JSON core in cURL can support that, too, accessing values to use for a comparison is extremely easy (but ads complexity to cURL, too).

Then you could habe a request/response maybe in one call.

Sure you may have a better idea... so don't hesitate to disagree... ;-)

Morten.

----- Original Message -----
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
To: curl users <curl-users_at_lists.haxx.se>
Cc: Daniel Stenberg <daniel_at_haxx.se>
Date: Thu, 20 Jan 2022 14:38:54 +0100 (CET)
Subject: JSON support

> Hello,
>
> I've been circling around this topic before. On this list I've previously
> gotten rather lukewarm responses or even several "don't do its", but after
> having asked around people on twitter I think maybe the time might come when
> we add some JSON specific command line options to the tool.
>
> I have three reasons why now:
>
> 1. Sending JSON has grown to become a very common thing to do in the world of
> REST APIs and more.
>
> 2. When asked what features or functionality people like in the many curl
> "alteratives" that pop up, the "ease of doing JSON" is a frequent answer.
>
> 3. A not insignificant amount of people on stackoverflow etc have problems to
> send correct JSON with curl and to get the quoting done right, as json uses
> double-qoutes by itself and shells don't expand variables within single quotes
> etc.
>
> I personally am not sending JSON too often myself so I'm pretty sure I'm not
> suitable to design this feature entirely on my own. I need help to design this
> to become as useful as possible.
>
> I've drafted my refreshed concept in the curl wiki. To explain it shortly, it
> adds two command line options: one for sending already formatted json as a
> shortcut for -d with the right Accept header, and the other is an option for
> building a json request body to send. See the expanded thoughts here:
>
> https://github.com/curl/curl/wiki/JSON
>
> That page was previously describing a slightly different json idea, so if you
> looked at it before, look again because it's different now.
>
> Is this a good idea? What tweaks does it need to become useful? If you're
> sending JSON with curl or an alternative tool today, could you see yourself
> using this method instead and what would be needed for that to be really
> attractive for you?
>
> --
>
> / daniel.haxx.se
> | Commercial curl support up to 24x7 is available!
> | Private help, bug fixes, support, ports, new features
> | https://curl.se/support.html
> --
> Unsubscribe: https://lists.haxx.se/listinfo/curl-users
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>
-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-users
Etiquette:   https://curl.haxx.se/mail/etiquette.html
Received on 2022-01-20