Hello,
having static name for htable there helped to do the lookup of hash table structure at startup and keep pointer to it for faster access as well as parse the part after => to break it in variables and static strings. Having it a dynamic value didn't seem useful at the time of implementation several years ago.
In the code is possible to lookup the hash table at runtime, being also done by some of the htable cfg functions. It will require some new code to evaluate the name expression every time at at runtime, then parse and lookup the hash table structure...
Cheers, Daniel
On 13.10.20 09:25, Juha Heinanen wrote:
Is there some good reason why htable in $sht(htable=>key) cannot be a dynamic string containing pseudo variables?
-- Juha
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users