Replace xmlrpc with maintained package?

[ajmas]

I recently ran into this issue, with odoo-await (caused by connecting to http port 80, while specifying https):

Error: write EPROTO 140596194441088:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

While investigating the issue it came to my attention that the xmlrpc library this project depends on has not been maintained for 5 years, and many of its dependencies for just as long. Given this, would it make sense to replace xmlrpc with a package that is currently maintained?

Edit: Looking around, I am not sure there is a good replacement. Some appear to be unmaintained forks, while others lack documentation, such as @foxglove/xmlrpc . Its possible that the unmaintained 5 year old package is still suitable?

[vettloffah]

Thanks for the suggestion, looking into this. But yeah, back when I first published the library I did some research and couldn't find any suitable replacements. Not sure if things have changed.

[vettloffah]

I discovered a new package here: https://www.npmjs.com/package/@foxglove/xmlrpc

It is meant to support one of the company's software products, but I think it would work as a general XML RPC client. I asked in their slack channel and they confirmed it should.

[RicardoViteriR]

Hi @vettloffah, what would be the general strategy to migrate to this package?

1. Setup testing environment with current tests
2. Migrate methods to the new client

[vettloffah]

Yes that should do it @RicardoViteriR