[issue1054434] automatic XMLRPC boxcarring via multicall for xmlrpclib

2008-03-29 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: As nobody has asked for this patch to be included, I think its probably easiest just to reject it. Thanks for offering it in the first place, though. -- resolution: -> rejected status: open -> closed ___

[issue1054434] automatic XMLRPC boxcarring via multicall for xmlrpclib

2008-03-25 Thread Ralf Schmitt
Ralf Schmitt <[EMAIL PROTECTED]> added the comment: I personally have no need for it (not even for non-automatic boxcarring). Note that you would also have to write documentation. -- type: -> feature request versions: +Python 2.6 -Python 2.5 _ Tracke

[issue1054434] automatic XMLRPC boxcarring via multicall for xmlrpclib

2008-03-24 Thread Eric Ries
Eric Ries <[EMAIL PROTECTED]> added the comment: This code is more than three years old, so the attached version has gone stale. Still, here at IMVU we have continued to use the xmlrpc boxcarring, and could probably provide an updated diff if desired. Let us know if this is a feature of interest.

[issue1054434] automatic XMLRPC boxcarring via multicall for xmlrpclib

2008-03-24 Thread Ralf Schmitt
Ralf Schmitt <[EMAIL PROTECTED]> added the comment: this issue is about the threaded one. I think it should be rejected. It does not work: ~/ python2.5 xmlrpclib_multicall.py [EMAIL PROTECTED] failed 1 Traceback (most recent call last): File "xmlrpclib_multicall.py", li

[issue1054434] automatic XMLRPC boxcarring via multicall for xmlrpclib

2008-03-22 Thread Guilherme Polo
Guilherme Polo <[EMAIL PROTECTED]> added the comment: I see these multicall classes (including tests) in python-trunk, except for the threaded one. So, should this remain open ? If yes, what has to be done here ? -- nosy: +gpolo _ Tracker <[EMAIL PROT