Alan Milligan wrote at 2004-10-13 11:31 +1000:
...
I appreciate that supporting 'unofficial' extensions to protocols is not
something we want to encourage, but is there any chance of getting this
patch into zope core (ever)?
I hope not...
--
Dieter
Hi,
Am Di, den 12.10.2004 schrieb Alan Milligan um 0:16:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I had a client that used to work on 2.7.0, and now doesn't on 2.7.3.
The problem would appear to be that it's not substituting the
xmlrpc.Response class for a GET request on a
Heh,
Yes - would you like to lobby RedHat to change their up2date client??
I think the reason they've done this is because it's much more efficient. Not only do
they not have to read the body, they don't have to parse it.
Also, xml-rpc is totally screwed because it doesn't have a file type,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tino Wildenhain wrote:
|
|I had a client that used to work on 2.7.0, and now doesn't on 2.7.3.
|
|The problem would appear to be that it's not substituting the
|xmlrpc.Response class for a GET request on a text/xml content type and
|therefore just
Hi,
Am Mi, den 13.10.2004 schrieb Alan Milligan um 3:31:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tino Wildenhain wrote:
|
|I had a client that used to work on 2.7.0, and now doesn't on 2.7.3.
|
|The problem would appear to be that it's not substituting the
|xmlrpc.Response class
According to the CHANGES.txt there were no changes to XMLRPC. xmlrpclib.py
was removed
before 2.7 final because it is part of the Python distro. Looking at your
debug output I have
no idea what it will show us.
Andreas
--On Dienstag, 12. Oktober 2004 8:16 Uhr +1000 Alan Milligan
[EMAIL
According to the CHANGES.txt there were no changes to XMLRPC.
xmlrpc.py is not faulty, it's just that an HTTPResponse object is assigned to the
text/xml content type rather than the correct xmlrpc.Request :(
___
Zope-Dev maillist - [EMAIL
I suggest to look at the cvs log output for that particular file to find
something.
-aj
--On Dienstag, 12. Oktober 2004 5:23 Uhr + Alan Milligan
[EMAIL PROTECTED] wrote:
According to the CHANGES.txt there were no changes to XMLRPC.
xmlrpc.py is not faulty, it's just that an HTTPResponse
