--- In [email protected], sgp acs322000 <[EMAIL PROTECTED]> wrote:
>> Why do you want to use WriteNamedPipe? If you want to communicate >> with powerpro, ppBang and <powerpro.exe> <command to send> will do the >> job. Is there some reason you want yet another means to send to PP? >> >I realize I have no real use for writenamedpipe as is, your model is what >I need to experiment creating a console front-end command-line to >powerpro, similar to pp2stdin but constantly connected to ppro. 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? Perhaps you want a console app that constantly listens for messages from pipe plugin? 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/
