[Kamailio-Users] "Permanent" AVP

[Antonio Reale]

2010/1/25 Henning Westerholt <henning.westerholt at 1und1.de>:

> from the performance POV this three ways make probably not that much a
> difference, but i'd differ them over the intendent use case:
>
> 1. global AVPs
>
> This is the oldest mechanism, i think they were implemented as a list in the
> core. In kamailio we moved them to the pseudo-variables, but they still have
> certain core parts. I'd use them if you've a smaller set of values to store,
> like one or two values you set during startup.
>
> 2. htable
>
> This is a mechanism coming from the kamailio side, they implement a hash table
> like you probably know from other languages as perl or java. As this implement
> a key-value storage which is basically arbitrary large (depending on the
> memory) i'd use them to store certain attributes, like the number of failed
> authentification per user (as described in the mod docs).
>
> 3. custom cfg params
>
> This is a mechanism coming from the SER side, i think. If I understand the
> docs correctly i'd use them if i have certain attributes which belong to a
> bigger group or class, like a hostname or simliar. Its probably easier to add
> structure to your values as if you use the (global) AVPs.
>
> Hope that helps,
>
> Henning
>

Hi Henning,
thanks for the clarification. It is exactly what I needed.

Regards,

-- 
Antonio