Re: multiprocessing and accessing server's stdout

2010-06-02 Thread Bryan
I wrote: > So what you really need is to capture the output of a command, in this > case LaTeX, so you can copy it back to the client. You can do that > with the subprocess module in the Python standard library. > > If the command generated so much output so fast that you felt the need > to avoid t

Re: multiprocessing and accessing server's stdout

2010-06-02 Thread Bryan
Tim Arnold wrote: > Hi, This is the setup I was asking about. > I've got users using a python-written command line client. They're > requesting services from a remote server that fires a LaTeX process. I > want them to see the stdout from the LaTeX process. So what you really need is to capture th

Re: multiprocessing and accessing server's stdout

2010-06-01 Thread Tim Arnold
On May 28, 7:47 pm, "Martin P. Hellwig" wrote: > On 05/28/10 21:44, Adam Tauno Williams wrote: > > > On Fri, 2010-05-28 at 15:41 +0100, Martin P. Hellwig wrote: > >> On 05/28/10 13:17, Adam Tauno Williams wrote: > >> > >>> You should be able to point it any any file-like object.  But, again, > >>

Re: multiprocessing and accessing server's stdout

2010-05-28 Thread Martin P. Hellwig
On 05/28/10 21:44, Adam Tauno Williams wrote: On Fri, 2010-05-28 at 15:41 +0100, Martin P. Hellwig wrote: On 05/28/10 13:17, Adam Tauno Williams wrote: You should be able to point it any any file-like object. But, again, why? If you have the data in the process why send it to stdout and redir

Re: multiprocessing and accessing server's stdout

2010-05-28 Thread Adam Tauno Williams
On Fri, 2010-05-28 at 15:41 +0100, Martin P. Hellwig wrote: > On 05/28/10 13:17, Adam Tauno Williams wrote: > > > You should be able to point it any any file-like object. But, again, > > why? > > If you have the data in the process why send it to stdout and redirect > > it. Why not just send the

Re: multiprocessing and accessing server's stdout

2010-05-28 Thread Martin P. Hellwig
On 05/28/10 13:17, Adam Tauno Williams wrote: You should be able to point it any any file-like object. But, again, why? If you have the data in the process why send it to stdout and redirect it. Why not just send the data to the client directly? Well you might want to multiplex it to more

Re: multiprocessing and accessing server's stdout

2010-05-28 Thread Adam Tauno Williams
On Thu, 2010-05-27 at 08:36 -0700, Tim Arnold wrote: > On May 26, 4:52 pm, Adam Tauno Williams > wrote: > > On Wed, 2010-05-26 at 11:47 -0700, Tim Arnold wrote: > > > Hi, > > > I'm using multiprocessing's BaseManager to create a server on one > > > machine and a client on another. The client fires

Re: multiprocessing and accessing server's stdout

2010-05-27 Thread Tim Arnold
On May 26, 4:52 pm, Adam Tauno Williams wrote: > On Wed, 2010-05-26 at 11:47 -0700, Tim Arnold wrote: > > Hi, > > I'm using multiprocessing's BaseManager to create a server on one > > machine and a client on another. The client fires a request and the > > server does some work, the result of which

Re: multiprocessing and accessing server's stdout

2010-05-26 Thread Adam Tauno Williams
On Wed, 2010-05-26 at 11:47 -0700, Tim Arnold wrote: > Hi, > I'm using multiprocessing's BaseManager to create a server on one > machine and a client on another. The client fires a request and the > server does some work, the result of which ends up on a shared file > system that both the client an

multiprocessing and accessing server's stdout

2010-05-26 Thread Tim Arnold
Hi, I'm using multiprocessing's BaseManager to create a server on one machine and a client on another. The client fires a request and the server does some work, the result of which ends up on a shared file system that both the client and server can see. However, I need the client machine to see th