eHTTPServer / BaseHTTPRequestHandler) ae designed the way they
are. The underlying stream medium (TCP sockets or plain file
streams like stdin/stdout) should not be integrated with the
protocol (HTTP) handling, IMHO...
--
--Jos Vos <[EMAIL PROTECTED]>
--X/OS Experts in Open Systems BV
On Mon, Apr 17, 2006 at 12:36:18PM +0200, Brian Quinlan wrote:
> I don't know exactly what your usage pattern is, but you might be able
> to use SimpleXMLRPCDispatcher directly e.g.
>
> >>> s = SimpleXMLRPCDispatcher()
> >>> s.register_function(pow)
> >>> s._marshaled_dispatch(' '
--X/OS
n XMLRPC subclass which reads from stdin and writes to
> stdout.
Will try...
--
--Jos Vos <[EMAIL PROTECTED]>
--X/OS Experts in Open Systems BV | Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
--
http://mail.python.org/mailman/listinfo/python-list
ll try it.
--
-- Jos Vos <[EMAIL PROTECTED]>
--X/OS Experts in Open Systems BV | Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
--
http://mail.python.org/mailman/listinfo/python-list
dler reading/writing from stdin/stdout,
i.s.o. carrying all the server class stuff with it.
--
--Jos Vos <[EMAIL PROTECTED]>
--X/OS Experts in Open Systems BV | Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
--
http://mail.python.org/mailman/listinfo/python-list
w I want it to
*not* do the binds etc. to listen on a port.
The problem is that the server initialization *requires* a server
address (host, port pair), but I don't see how to tell it to use
the stdin socket (and I'm afraid this is not possible, but I'm not
sure).
--
--Jo
iting via stdin/stdout).
Any hints or code examples?
Thanks,
--
-- Jos Vos <[EMAIL PROTECTED]>
--X/OS Experts in Open Systems BV | Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
--
http://mail.python.org/mailman/listinfo/python-list
