break appeared early in SER; so, it remained. drop is a tad newer (?) and probably appeared in the tradition of packet filtering naming. there is also the more intuitive "exit" alternative to it. there is also a "return" alternative for break.
WL.
On 8/6/07, SIP sip@arcdiv.com wrote:
Weiter Leiter wrote:
On 8/6/07, *tzieleniewski* <tzieleniewski@o2.pl mailto:tzieleniewski@o2.pl> wrote:
Hi, Is there any difference in the brake and drop command behavior in ser.cfg??break stops execution of current route, resuming the next outer one (if any), from where the current was invoked. drop stops execution of script.
WL.
I'm assuming these are SER 2.0 commands?
Is it possible to have come up with even more convoluted and non-intuitive names? Perhaps "frog" and "bunny" or "seratonin" and "cuisinart" ? I mean, why stop with 'brake,' which is so close to being 'break' (the command one usually uses in a programming setting to escape a loop) and yet... isn't. Or drop... which really doesn't imply to me 'stop execution' as much as it implies ignore an incoming connection... or perhaps delete a table.
N.