Gaetano Giunta

Mostly done - but docs have to be rewritten from scratch given the big API changes, and the whole process tested

The user manual rewrite is a WIP. Otoh the API docs are now generated using Sami, and for version 4.0.0 have been uploaded to http://gggeek.github.io/phpxmlrpc/doc-4/api/index.html

Back from Sami to PhpDocumentor

Thanks a lot for taking time to run this analysis and posting the resulting issues. However, as with any automated security scanning tool, there are risks of generating false positives...

Hello. It seems that I can not find the relevant source any more, but I am pretty sure that when the discussion came up (probably on the xmlrpc mailing list)...

ps: found at least a link backing up the above: https://groups.yahoo.com/neo/groups/xml-rpc/conversations/topics/6752

Thanks for the suggestions. Checking for function names instead of presence of a specific extension and adding a transcoder class seem like good ideas. The only downside is that, if...

That looks like a network error condition, possibly a transient one. In any case it is not related to this library, but to Composer, which is a 3rd party tool....

I do get a 404 for https://repo.packagist.org/p2/vendor/package.json. Otoh when I run the very same command `composer require phpxmlrpc/phpxmlrpc:4` locally, it works - with composer 2.1.5 using curl 7.68.0.

PS: I asked the lead dev of Composer, and he said that the problem is in the curl timeout, not in the fact that composer tries to access that page....