@lazedo - actually the PR saving new field in xavp is merged. I suggested at that time to
add an option to control what is added, because more and more fields were wanted in the
xavp and they were stored by implicitly -- that was the what every developer did before.
So all these were following the previous pattern - save implicitly. With this new PR there
is an option for fine control. I think it is better to have a straight rule -- with
default option: save all fields or don't save any, then this parameter comes to do
selective decision on saving specific fields. The preference was to store all and have
option to skip -- from my point of view could have been also the opposite: don't store
any by default and specify what to store.
I think it would be a bit more confusing/unnatural to have a "default random list of
stored attributes".
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2168#issuecomment-563355457