10 Dec
2009
10 Dec
'09
7:08 a.m.
Daniel-Constantin Mierla writes:
t_on_reply("1"); - run onreply_route[1] with
no locking (default, same
syntax as now) for current transaction.
t_on_reply("1", "0"); - run onreply_route[1] with no locking for
current
transaction.
t_on_reply("1", "1"); - run onreply_route[1] under lock for current
transaction.
fine, if t_on_reply("1") is equal to t_on_reply("1", "1").
this is very
important for backwards compatibility and error prevention.
t_on_reply("1", "0") is then for optimization purpose.
-- juha