Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
avpops: no DB caching, so no need of "reload" - it just read from DB each time.
i was thinking that it might make sense to have also shared memory, transaction independent avps to store information that is dynamic, but does not change often.
I'm already considering adding two types of AVPs: - script avp - not attached to any transaction they will leave only during a route - excellent to perform temp operation in script without carrying about sync, removing them, etc.... - global avp - which will be visible everywhere in OpenSER, for all messages - they will be used to control overall behaviour of OpenSER and they will be provision via external cmds or DB table - something like gflag for flags.
you can see script AVPs as a particular case of global AVPs (limited life time) and may be skipped :).
The only issue here is know to specify the AVPs in order to make distinction between the AVP types in their specifications....which is global and which is per transaction and so on....
regards, bogdan