Message76343
This patch makes sense in principle, but some of the details need to
change. The _send_output() method is used by some clients, merely
because it can be used :-(. It's fairly easy to preserve this API for
backwards compatibility.
I am also worried about this new api call getheaderdata(). It
complicates the API. Even if it were necessary, it needs a better name,
because getheaderdata() doesn't sound like a method that changes the
connection state or consumes buffered header data.
I think it would be better to have the new behavior exposed only through
HTTPConnection and not HTTP, since that's a Python 1.5.2 compatibility
API(!). We can make some small changes to xmlrpclib to use the newer
API. It would probably be a good change merely because py3k now uses
the newer API.
I've got a working local change, but it's still a little ugly. |
|
Date |
User |
Action |
Args |
2008-11-24 17:32:15 | jhylton | set | recipients:
+ jhylton, kristjan.jonsson |
2008-11-24 17:32:15 | jhylton | set | messageid: <1227547935.56.0.907800385246.issue4336@psf.upfronthosting.co.za> |
2008-11-24 17:32:14 | jhylton | link | issue4336 messages |
2008-11-24 17:32:14 | jhylton | create | |
|