Tom, Sounds like a classic application for sockets. Inter process communications.
Phantom 1 opens a server socket on a known port/IP and waits on a blocked read for something (like a process name to run for example). Process 2 opens a socket on the known port/ip and writes the name of the process it would like to have run and perhaps provides some parameters as either a command line or second write. Process 1 fires off the requested process and writes and response. Tom Whitmore wrote: > We have two phantom processes. The first phantom needs to wait for an event > to occur with the second phantom. I realize that I could have the first > phantom loop, check, then sleep. However, I'd like to avoid wasting > resources. Back on the Prime, I could use semaphores, to control this flow > and this was clean, and simple. Has anyone come across a means of having a > phantom wait on "something", so it only wakes up when it needs to perform its > function? > > To try to explain better: > > Phantom1: > Loop > Wait on semaphore > Perform a shared process (batch updates would be an example) > Repeat > > > Phantom2 (3, 4, ...): > Loop > Process records > Notify semaphore > Repeat > > Thanks, > Tom Whitmore > RATEX Business Solutions > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > > -- ------------------------------------------------------------------------ Jeff Schasny - Denver, Co, USA jschasny at gmail dot com /"Come To The Dark Side, We Have Cookies."/ ------------------------------------------------------------------------ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
