Re: Beyond IKC/monitor : SENDER, session death and more

[gwynp]

On 27-Jun-2001 Artur Bergman wrote:
> Ok, could somone tell me, what do you people want to monitor. I am lost.

The list again, with annotations :

Monitor triggers are one of :
    on_stop  (when a session is GCed)
                This way IKC can tell remote kernels to kill proxied
                sessions.
    on_error (wrap event calls in eval {}, pass $@ to monitor event)
                This way I can isolate exception handling code.
    on_oops  (non-fatal, but annoying things like posting to non-existant
              sessions/events)
                IKC could use this for message routing.
    on_log   (generalized logging mechanism)
                Maybe not the best idea, but something along these lines
                is very very useful for large applications
    on_child (child session created... useful for debuging)
    on_post  (called when an event posts/calls other events... useful for
              debugging and other things)
                Scripting could be implemented via this feature.  Could be
                used to track if an IKC thunking session should stay alive.

-Philip