*nods* My applications do the exact same thing and absolutely thrive on intersession calls. No touchie. :) Thanks.
On Wed, 11 Feb 2004, Nick Williams wrote: > I have a fairly complex system that runs various background monitoring > tasks (using Wheel::Run) and also takes in requests from the network. > Each new network request gains its own session for it to process all > work. This work may take some time, also creating new Wheel::Runs, etc. > The effect of some of the requests needs to change the frequency of the > background monitoring that's going on, or needs to change some of the > 'global' data that dictates the manner in which the background > processing is run. There is no synchronisation/locking of global data, > so the only way to do that is to ask the session owner to make the > change. When that type of event happens, we need to get a cross-session > event to take place. We can't use post() all the time, because sometimes > we need to ensure that the change happens before anything else in the > queue is fired off, else we get out-of-order processing. It's a rare > thing (only need this twice, in a codebase of ~20k lines of perl), but > it does happen. I cannot see (within the constraints of our > architecture) how I can achieve this without inter-session call > functionality. > > Nick. >
