Thank you much! For some reason, while reading the docs, I had missed that.
That should do nicely. j On Friday, October 19, 2012 08:59:24 Tomer Filiba wrote: > See: > > http://rpyc.sourceforge.net/docs/servers.html#general-switches > > And: > https://github.com/tomerfiliba/rpyc/blob/master/scripts/rpyc_classic.py#L97 > > On Oct 19, 2012 8:54 AM, "Joshua J. Kugler" <[email protected]> wrote: > > So, I'm looking for an RPC library. I found > > http://code.google.com/p/rfoo/ > > but it seems to have fallen out of maintenance. > > > > However, one of the reasons rfoo caught my eye was that both the server > > and > > the client could take arbitrary stream pipes (even stdin/stdout) as their > > connection. > > > > This would make it possible, for example, to spawn the RPC server from > > something like xinetd. The script would start up, hand sys.stdin and > > sys.stdout to the rpyc server, and then invoke the server. Like wise, the > > client could have a plain stream connection and just write to the socket > > and > > read from it. > > > > From initial reading of the docs, and looking at the API, this does not > > seem > > possible. If I am correct, could someone confirm that? If I am incorrect, > > could someone point me to an example of using stdin/stdout as the servers > > stream? > > > > Thanks! > > > > j > > > > -- > > Joshua J. Kugler - Fairbanks, Alaska > > Azariah Enterprises - Programming and Website Design > > [email protected] - Jabber: [email protected] > > PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design [email protected] - Jabber: [email protected] PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
