WG> Here's a possibly creative solution to the problems 
 WG> you've been talking about. How about we add a new 
 WG> "RouteStop" keyword to Squish, which behaves like 
 WG> Route, except it means "if this routing keyword did 
 WG> work, stop processing that packet on this run"?
 WG>  
 WG> It might seem a little connvoluted from a ruting 
 WG> requirements point of view, but it should be reatively 
 WG> easy to implement without risking breaking any other functionality.

We're thinking in similar ideas, just slightly different implementation. 
I'd put a new keyword in squish.cfg that changes the meaning of send and
route to mean by what you state as RouteStop in route.cfg.....  Same
process thou....

And again, just a low level (back burner) request....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01