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: [brain-storm] Can we make JSON posting easier?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_cool.haxx.se>
Date: Thu, 17 Jun 2021 09:10:58 +0200 (CEST)
On Wed, 16 Jun 2021, James Fuller wrote:
> 1) clearly document this usage with tools like jq and curl ...
This would be great, I agree and could become a great resource for JSON using
curl users. I think "everything curl" would be the ideal place for such
documentation. Unfortunately I'm not the man to write it since I've only used
jq a few times and I certainly am not fluent in it.
> I also think the curl man page (on curl.se) should be the first link anyone
> can see ;)
Website design and layout is hard and I suck at it, so sure if you (the
collective you) have ideas on how to make the man page more prominent in a
good way, I'm all ears!
> 2) we might provide a separate tool for preparing request bodies - that tool
> could have extensibility points for json and possibly other formats
When we're talking separate tools, I don't think we can or should even try to
compete with jq. Is there something we can or should do in order to work
better or smoother with jq?
> 3) similarly, we might provide some hook to external script for pre
> processing of contents of --data
If that provides some better functionality than using a plain pipe I wouldn't
mind that. But I can't think of any such advantages right now. Can you?
Date: Thu, 17 Jun 2021 09:10:58 +0200 (CEST)
On Wed, 16 Jun 2021, James Fuller wrote:
> 1) clearly document this usage with tools like jq and curl ...
This would be great, I agree and could become a great resource for JSON using
curl users. I think "everything curl" would be the ideal place for such
documentation. Unfortunately I'm not the man to write it since I've only used
jq a few times and I certainly am not fluent in it.
> I also think the curl man page (on curl.se) should be the first link anyone
> can see ;)
Website design and layout is hard and I suck at it, so sure if you (the
collective you) have ideas on how to make the man page more prominent in a
good way, I'm all ears!
> 2) we might provide a separate tool for preparing request bodies - that tool
> could have extensibility points for json and possibly other formats
When we're talking separate tools, I don't think we can or should even try to
compete with jq. Is there something we can or should do in order to work
better or smoother with jq?
> 3) similarly, we might provide some hook to external script for pre
> processing of contents of --data
If that provides some better functionality than using a plain pipe I wouldn't
mind that. But I can't think of any such advantages right now. Can you?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ----------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2021-06-17