#### Pre-Submission Checklist <!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply --> <!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above--> <!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list --> - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist: <!-- Go over all points below, and after creating the PR, tick the checkboxes that apply --> - [ ] PR should be backported to stable branches - [x] Tested changes locally
#### Description
expose in config via cfgutils ``core_case_hash`` optional second string key for hashing
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3808
-- Commit Summary --
* cfgutils: expose optional second string key for hashing at locks * cfgutils: document second optional string for hashing on lock functions family [skip ci] * app_lua_sr: support second str for cfgutils lock
-- File Changes --
M src/modules/app_lua_sr/app_lua_sr_exp.c (30) M src/modules/cfgutils/api.h (4) M src/modules/cfgutils/cfgutils.c (103) M src/modules/cfgutils/doc/cfgutils_admin.xml (18)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3808.patch https://github.com/kamailio/kamailio/pull/3808.diff
I have nothing explicitly against this enhancement, but I guess that if one wanted to have two strings to compose the lock key, then could use `lock("$var(str1)$var(str2)")` as alternative to new variant `lock("$var(str1)", "$var(str2)")`. The hashing behind is probably not the same result, but from the perspective of taking in consideration two strings for hashing, should be a similar behaviour.
Merged #3808 into master.