> I wouldn't. I would recommend using a sophisticated networking library > like Java or whatever your favorite language is on the JVM.
Can't figure out if you're kidding... > Who told you that? My employer offers a cURL port for z/OS and it's well > maintained with support for production environment. Ok, Rocket's curl? What's the percentage of clients that want a separate product for something that also comes with (or at least used to?) the OS (Ported Tools). Yes, everything I'm saying is subjective... Adoption would be much higher if Ported Tools' curl were actively developed. Eh ... I didn't say curl-ing a script is dangerous and CWET isn't. I meant piping any source-unknown script direct for execution is not a great idea. - KB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, July 24, 2020 8:53 AM, David Crayford <dcrayf...@gmail.com> wrote: > On 2020-07-24 11:12 AM, kekronbekron wrote: > > > Just mentioned ASM / COB CWET for options really. > > They're a a lot more involved than the Python client (when that's > > available). > > curl is ok as a user, but when you want to productionize something, I would > > think the recommendation would be to use CWET. > > I wouldn't. I would recommend using a sophisticated networking library > like Java or whatever your favorite language is on the JVM. > > > Not saying curl is a bad tool, it is handy & does what it does. > > Ease of use does not mean it's the solution of choice in many controlled > > environments. > > By loved I mean does it get upgrades/improvements? > > Who told you that? My employer offers a cURL port for z/OS and it's well > maintained with support for production environment. > > > I don't know I'm just asking.. > > curl-ing a shell script directly is bit ... dangerous. > > That's purely subjective. I don't see why cURL would be any more > dangerous than writing a Python script or using CWET. > > Lots of people are using Git for DevOps on z/OS and that uses cURL for > ssh and https transport. > > > Not in this case as the script is available to inspect. > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
