Issues with rTorrent about node-xmlrpc HOT 6 CLOSED

For system.listMethods, the problem is indeed the string being too big. Several data events are fired in the client. Looks like some sort of buffering is needed.

from node-xmlrpc.

@ProjectMoon - Can you add a gist of the long system.listMethods response? I'll add it as a test case.

from node-xmlrpc.

Yeah... I tried using xmlrpc-c's command, but it parses the XML. I'll try to extract it from a call using modified version of this (i.e. console.log)

from node-xmlrpc.

@ProjectMoon: with your e725a05 commit and my newline fixes, it seems like this command is now working :)

I'll make a pull request soon.

from node-xmlrpc.

e725a05 and a test case for chunked responses were added in the 0.7.1 release. Please let me know if you have any more issues with chunked responses @ProjectMoon.

I believe the other issue mentioned in this ticket is because i8 is not currently supported in the parser, only int and i4 types. There's no native 64-bit integer handling in node, so either an approximation of the value from being interpreted as a JavaScript number or by some module that adds 64-bit integer support. I added another ticket to address i8 support specifically.

Thanks again @ProjectMoon for the help.

from node-xmlrpc.

Yeah I can confirm there are no longer any issues with system.listMethods, as I'm also working with rtorrent.

from node-xmlrpc.