If that's the best option, then I guess it's the way to go. I was hoping to relieve process A of having to maintain an explicit signalling link with process B, apart from the mapped file itself. True, I can't see how that might be achieved, but I want to check I'm not missing anything.
On Sat, Apr 30, 2011 at 2:30 AM, Henry Rich <[email protected]> wrote: > Use sockets? > > Henry Rich > > On 4/29/2011 9:14 PM, Ian Clark wrote: >> Suppose I have two J tasks A and B sharing a mapped file F. How can B >> best get to know that A has just changed F? >> >> AFAICS, B needs to execute a duty-cycle inspecting the directory >> timestamp of F using 1!:0 (which may delay for up to a second), or >> alternatively watch for a checksum to change on F's contents (if it's >> large). >> >> Before I do, is there some JAL facility I've overlooked? Ideally, the >> very act of A changing F should send a message to B -- a system event, >> say, that can run a callback. >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
