Skip Menu |

This queue is for tickets about the RPC-XML CPAN distribution.

Report information
The Basics
Id: 58065
Status: resolved
Priority: 0/
Queue: RPC-XML

Owner: rjray [...]
Requestors: mkanat [...]

Bug Information
Severity: Normal
Broken in: 0.73
Fixed in: 0.74

Subject: Client should always understand <nil/> in responses
Download (untitled) / with headers
text/plain 284b
I think in the Postel sense of being liberal, RPC::XML::Client should *always* understand <nil/>. There's no reason it should throw an error just because it receives <nil/>, when RPC::XML has the support to decode it. Of course, it should never *send* nil unless ALLOW_NIL is set.
Download (untitled) / with headers
text/plain 403b
I'm extending this to include Server as well. You won't be able to explicitly encode a null unless you've set the flag, but the parsers will handle nil tags regardless of the flag's setting. Randy -- """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Randy J. Ray Silicon Valley Scale Modelers:
Download (untitled) / with headers
text/plain 331b
Fixed in git ( Will be in the next release. -- """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Randy J. Ray Silicon Valley Scale Modelers:

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to