Crybaby Grows up

[Bob Sneidar]

Just depends on what your scripts do. If your utility scripts are  
trying to intercept normal handlers and execute BEFORE the messages  
get to anything else, you would want them in front. If your scripts  
want to execute AFTER everything else may have possible gotten the  
messages, you would want it in back.

I think the general idea was, that if you opened a substack, you would  
want that stack's handlers to execute first, since you might be doing  
something special in that stack. Also, if a common message like  
openstack was intercepted, and then NOT PASSED, and your library was  
in the back, it would never get the openstack message.

Some think it's a good idea to always pass the message on unless you  
specifically want to stop the message when you intercept it. I  
subscribe to that notion myself. I think I learned that at the  
Monterey conference from either Trvor or Jerry. So I always include a  
pass statement at the end of my handlers unless otherwise intended.

Bob Sneidar
IT Manager
Logos Management
Calvary Chapel CM

On Feb 27, 2009, at 11:36 AM, DunbarX at aol.com wrote:

> Is there anything to discuss about why putting the msg stack script  
> into
> "back" is not a good idea?
>
> Craig Newman