[Zope] ANN: Zope XML-RPC!

Robin Becker robin@jessikat.demon.co.uk
Sun, 20 Jun 1999 17:14:05 +0100


In article <19990620100249.W14374@moebius.dartmouth.edu>, Eric Kidd
<eric.kidd@pobox.com> writes
>On Sun, Jun 20, 1999 at 02:09:13PM +0100, Robin Becker wrote:
>> a bit more debugging reveals that with the corrected URL I'm getting
>> back to HTTPRequest at line 203 with the response body being
>> response.body=
>> <?xml version='1.0'?>
>> <methodResponse>
>> <params>
>> <param>
>> <value><string>Hello, aaa!</string></value>
>> </param>
>> </params>
>> 
>> </methodResponse>
>> 
>> ie the xml handling is working at that level and seems to go wrong after
>> the function call is made.
>
>This looks like a good response. But you definitely shouldn't be seeing a
>fully formed response on line 203 of HTTPRequest:
>
>  202:meth, self.args = xmlrpc.parse_input(fs.value)
>  203:response=xmlrpc.response(response)
as far as I can tell this is the only place where HTTPRequest interacts
with XML-RPC so it appears correct that the body should have happened
here.  I don't seem to have the same code as you so maybe that's the
problem.
>
>At this point, the response object has just been created. You shouldn't be
>getting a valid response body until the object has been published, which
>requires making it back out to line 256 of Publish:
>
>  255:response=request.response # could have changed!
>  256:response = publish(request, module_name, after_list, debug=debug)
>
>Or am I missing something really obvious?
>
>Cheers,
>Eric
>
>_______________________________________________
>Zope maillist  -  Zope@zope.org
>http://www.zope.org/mailman/listinfo/zope
>
>(For developer-specific issues, use the companion list,
>zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

-- 
Robin Becker