Front page | perl.perl5.porters |
Postings from June 2022
------- Original Message ------- On Thursday, June 16th, 2022 at 15:58, Darren Duncan <darren@darrenduncan.net> wrote: > THIS IS A DUPLICATE RESPONSE. I HAD PREVIOUSLY SENT THE SAME THING UNDER AN > ALTERED SUBJECT LINE. REPEATED TO KEEP IT TOGETHER WITH THE MAIN THREAD. ALSO A DUPLICATED ANSWER :-) > > I propose an alternate solution, summarized as bootstrapping. > > Perl bundles an implementation of HTTPS support including certs or whatever, so > there is zero dependency on any HTTPS library or files being with the operating > system. While I understand Darren proposal's goal, and at some point it makes sense, I do not think it is the solution more interesting to Perl developers and Perl itself. This suggestion is almost like including an HTTP client that can just connect to CPAN, and if you want to connect to anywhere else, then download a module from there. But this is not the case. Perl ships with a fairy good, although tiny, implementation of a HTTP Client. And nowadays, you almost do not need anything else to perform HTTP connections. Nevertheless, not having HTTPS support makes it, day by day, more useless without extra modules. Thus, I do not think it is worth the effort of streamlining an SSL library to ship with code to just connect to one specific host. Of course, just my 5 cents for the discussion :-) Kindest regards, Alberto (aka ambs)Thread Previous | Thread Next