[asterisk-dev] Realtime caching or something else? (SIP
retransmit #1)
Sergey Okhapkin
sos at sokhapkin.dyndns.org
Tue Oct 31 06:21:45 MST 2006
To my understanding, most of asterisk users (including myself) want static
realtime (item 2 in your list).
On Tuesday 31 October 2006 07:59, Olle E Johansson wrote:
> I don't want to continue fixing a broken implementation. My suggestion:
>
> * Implement real caching: A configuration option that says how many
> devices we should
> keep in memory (a max level) and a way to determine which ones to
> expire when we hit
> this level. Do *not* provide NAT keepalives or MWI for these.
> Maybe we need manager/CLI commands for deleting cached objects that
> have changed
> in the database.
>
> * Implement static realtime: When a device registers, load it in
> memory from realtime
> storage and keep it in memory. Provide services like NAT keepalives
> and MWI during registration.
> Only delete these from memory when they unregister or registration
> expires.
>
> * We could additionally implement manager commands (and CLI) for
> forcing a load
> into memory from static storage. So if you configure for static
> and add a device during
> runtime, there's no need for full reload, just tell asterisk that
> there's a new device
> that needs to be loaded into memory.
More information about the asterisk-dev
mailing list