Hello David,
Le Mar 14 Juin 2016 04:42:57, DAVEWOOD a écrit :
Show quoted text> I couldnt find any information about the state of Net::DRI so I'm
> writing here in hope that others can find it too.
Still actively maintained, used on the field, with at least 2 active forks on github.
Show quoted text> Net::DRI 0.96 doesnt build and has been removed from debian
> repositories.
It is indeed an old release.
0.96_09 was released not long ago, and should run correctly everywhere, it passes all tests, including with new Perl versions.
I'm trying currently to release more often and shrunk as much as possible my long TODO list of outstanding problems.
It is marked as experimental only because some transports (basically HTTP) do not work anymore, which makes Net::DRI as a toolkit less useful, even if all the classic EPP parts (over TCP/TLS) works perfectly.
I would like very much to release a version marked as stable even if the current ones marked as experimental are as stable as they can be. This year would be good, but I can make no promise, as there are on the side also many other things
If I could find some resellers interested to implement some registrars API over HTTP (REST, SOAP, and SOAP-WSDL) it sure would go faster.
Also I could drop officially support for the relevant broken HTTP transports, even if I re-add them later. Fastest way, but this gives fear that they will never be put back where I still have the hope to have Net::DRI used for other things than just an EPP client. Maybe I'm too much a dreamer.
If you have any ideas or points to add, feel free to let me know.
Show quoted text
These were 2 bugreports in 2013 where indeed Net::DRI was not taking into account some features of newer Perl version (just because I was stuck with old versions of Perl), such as hash keys randomization. This has been also fixed long ago.
Currently I see cpantesters showing all tests as OK under all versions of Perl starting with 5.10
(support for 5.8 was dropped and clearly announced as such, when I started to use // and state operator) for thhe 0.96_09 version.
I'm putting this bugreport as "stalled" to let it visible to others if that may help, and I will close it when I release a 0.97 (or even 1.00) version.
Any comments and feedback is welcome.
Regards,
