--- In [email protected], sgp acs322000 <[EMAIL PROTECTED]> wrote:
> entropyreduction wrote:
> 
> yes, I had changed the default authorization to my machine name. The 
> sendtoself and sendto and listento scripts were working fine among 
> themselves. listento failed when I started using the external
> pipewrite

WriteNamedPipe from
http://gearbox.maem.umr.edu/fwu/

says if exec'ed without params

 "named pipe (byte-mode, duplex) is created..."

Okay, first problem: pipe plugin creates pipe using flavour
PIPE_TYPE_MESSAGE, not PIPE_TYPE_BYTE.  If it's needed I may
be able to add a parameter to the listen_on service to make it
either create byte or message pipe types.  Lemme know if you want it.
Byte-oriented is less appropriate IMO: communications to PP will
always be small packets of info (command, variable value), not a
continuous byte stream.

Also: if you run pipe.listen_on,  _it_ creates a named pipe, and waits
on input. 

I'm not sure that's gonna work.  My process has blocked waiting for
someone to do a WriteFile to me; WriteNamedPipe has created a
pipe and is hung, waiting for someone to execute a ReadFile.

Incompatible models, I think. God knows what's happening if they've
both created pipes with exactly same name, but it's gotta be ugly....

About having to do waits:  my sample scripts e.g.
  pipePluginTestScriptToSelf.powerpro

do a 3000 msec wait.for between send_to's.  That's mainly cause it
was a handy number when debugging.  The script works fine if
I remove the waits. 

I haven't tried to do the same when sending across the LAN using
pipePluginTestScriptListen.powerpro,
pipePluginTestScriptToOther.powerpro

The method I'm using for handling pipes will inevitably have overhead:
server waits on a message, receives message, _then disconnects
from the client_, leaving itself available for messages from other
clients. 

That means if you do a series of send_to's from the same client,
the pipe connections will have to be remade for each one. 

A classic way to improve throughput is for the listener to respond to
any attempt to connect by creating another pipe, that will be
dedicated to that particular client.  I could implement that; it would
mean adding new services (connect/disconnect).  Let me know if you
need it.


 







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/
 



Reply via email to