Inter-process communication, how? Part 2

[ecir.hana at gmail.com]

On Dec 23, 4:54 am, Dennis Lee Bieber <wlfr... at ix.netcom.com> wrote:
> On Sat, 22 Dec 2007 17:56:05 -0800 (PST), ecir.h... at gmail.com declaimed
> the following in comp.lang.python:
>
> > just to recap: last time I asked how to do an interprocess
> > communitation, between one Manager process (graphical beckend) and
> > some Worker processes.
>
>         Never considered a graphical control process as a "backend"
> before... Backend processing, to me, implies some sort of server without
> a user interface.
>
> > However, I would like to ask another thing: I would like to collect
> > everyting what the Workers print and display in Manager. Or, redirect
> > all Workers' stdout to stdio of Manager. If there was only one Worker
> > I could use a pipe, right? But if there are more than one Worker, what
> > to do? I found something called "named pipe" which seems rather
> > complicated. Then I thought I could somehow (how?) create a fake
> > (virtual) file object, redirect stdout of a Worket into it and from
> > there send the data to Manager via sockets. Please, what do you think?
>
>         I'd forget about stdout as a data communication means... The parent
> should probably set up a socket that accepts messages from any worker...
> or create a "reply" socket for each worker, and pass the worker the port
> on which the master expects to retrieve its output.

Ok, but how to redirect "print" statement into a socket?

>
>         "Named pipes" are, I think, a M$ Windows creation (though I think
> the Amiga supported disjoint pipes by using "run program >pipe:name" and
> "program <pipe:name" instead of "program | program"http://stason.org/TULARC/pc/amiga/faq/2-5-1-Using-PIPE-in-a-standard-...
> -- "run program" being ~ "program &" in most UNIX-based shells)
> --
>         Wulfraed        Dennis Lee Bieber               KD6MOG
>         wlfr... at ix.netcom.com             wulfr... at bestiaria.com
>                 HTTP://wlfraed.home.netcom.com/
>         (Bestiaria Support Staff:               web-a... at bestiaria.com)
>                 HTTP://www.bestiaria.com/