Steve,
Thanks for your reply, I'll look into things based on your comments.
Also, I've read your book "Python Web Programming" and wanted you to
know it has helped me a lot with various python projects, thanks!
Doug
--
http://mail.python.org/mailman/listinfo/python-list
Steve Holden wrote:
> Usually a "broken pipe" message is to do with disruption of a Unix pipeline
> rather than a network
> connection. I've seen the message mostly, IIRC, in BSD-based environments.
the socket layer uses EPIPE to indicate that a socket has been shut down
by the remote end.
writeson wrote:
Duncan,
Thanks for the reply. We are running this on an Apache server on the
linux box, and an iPlanet4.1 server on the solaris machines. However,
both these servers are strictly 'inside' the firewall. I checked the
apache configuration and there is no limitrequestbody parameter in
Duncan,
Thanks for the reply. We are running this on an Apache server on the
linux box, and an iPlanet4.1 server on the solaris machines. However,
both these servers are strictly 'inside' the firewall. I checked the
apache configuration and there is no limitrequestbody parameter in the
file at all
writeson wrote:
> Since then he's run into a problem. If he sends a query that gets a
> very large recordset from the database the script fails and it vaguely
> reports about a "broken pipe", which I'm guessing is a problem with the
> network connection. Has anyone else seen this use XMLRPC and Py
