Can you give some example of your use cases for them?
I cannot say for sure, but my intuition is that if you have three hundred
variables in any program, you're doing something wrong. At that point you're in
territory that clearly calls for some sort of non- scalar data structure, such
as an
or a dedicated module :)
On Feb 20, 2014 5:38 PM, Alex Balashov abalas...@evaristesys.com wrote:
Can you give some example of your use cases for them?
I cannot say for sure, but my intuition is that if you have three hundred
variables in any program, you're doing something wrong. At that
We have defined dedicated AVP variables for each feature. For example, SIP
Trunks or Subscribers or Media Handling or Header Manipulation etc, So the
no of variables (AVP) has been increased in the initialization.
At an instance the no of AVP's used/active might be quite low as each avp's
are
AVPs are in shared men and protected by locks. VARs are not.
There shouldn't be a big impact on using lots of them. Are you experiencing
any issues?
Regards
Ovidiu Sas
On Feb 20, 2014 7:32 PM, Jijo realj...@gmail.com wrote:
We have defined dedicated AVP variables for each feature. For example,
Maybe you should replace AVPs with VARs where needed. Vars are more
lightweight and with a per-process scope only.
Regards,
On Thu, Feb 20, 2014 at 9:38 PM, Ovidiu Sas o...@voipembedded.com wrote:
AVPs are in shared men and protected by locks. VARs are not.
There shouldn't be a big impact on
