entropyreduction wrote: > I'm fiddling aroudn with a standalone a variant of writenamedpipe. > However, I can't see how a pipe-writing colose app compatible with > pipe plugin would be "constantly connected to ppro". > > In an environment where listening pipe is meant to be constantly > available, a console-based writenamedpipe could do no more than send a > message and exit?
I was under the impression - probably wrong at this point - that pipe plugin could listen on multiple pipes, in which case I'd create a script that spawns a ppro event that constanly sits on a pipe waiting for input from a given instance of the console app. So script 'StartConsoleSessions' waits on pipe 'ConsoleRequests', when a request to start a console session comes in on that pipe, StartConsoleSessions spawns event id X, and returns X, via the pipe, to the console program. Now event id X and console program use pipe 'Session'++X to communicate. Is this possible? Conceptually flawed? Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
