Hello,
if one is concerned about the efficiency of some config snippets, then
use the benchmark module to see which is faster. Practically, that is
the scope of the module.
Cheers,
Daniel
PS. Indeed, the conditionals try to stop as soon as possible in case of
and/or tests.
On 10/16/07 17:34, Klaus Darilion wrote:
Andreas Granig wrote:
Hi,
AFAIK the conditions are checked in the order they appear and stop
as soon as possible. In your case in != INVITE it should be the same.
Further, if you use is_method("INVITE") it is even faster.
To be honest, I don't think it really cares in standard scenarios. An
optimization of some microseconds is next to nothing compared to the
duration it takes to perform a db or radius request for example.
that's true
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
