zenichev left a comment (kamailio/kamailio#4787)
I have two approaches that I can offer.
First approach:
1. I keep the global locks per table (all of them: trusted, address, domains),
this is by default (not harmful).
2. I introduce a modparam that controls whether the implementation of
containers is older (locks-free linked lists) or the newer one with hash tables
which are locks safe.
Second approach:
1. Second module with all of what's been introduced here by default and the
co-exists in parallel.
Second approach is less attractive tbh, because this means we will have to keep
both of them consistent over the course of time. Which gives a space for human
mistakes while maintaining both modules.
Also the first approach is smoother for those people who want to do the switch,
meanwhile the second way requires them to load another new module, which will
sound to them as a heavier step.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4787#issuecomment-4854430508
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4787/[email protected]>
_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
