Alex Hermann writes:
I went over tm documentation again, but couldn't
find any setting or function
to reset/ignore ruri.
Maybe there is some internal state keeping track of the ruri changes. In that
case, i'll adjust the patch to use ruri only depending on that
state. Somebody will have to tell me where that state is kept though.
every time t_next_contacts() is called, it rewrites request uri with
first remaining contact and if there are other contacts with the same q
value, it appends then as branches.
what is wrong with that?
-- juha