Re: Message store (Was: EMI: Serious Problem PANIC: Too many concurrent allocations)

On Wed, 12 Jun 2002, Aarno Syvänen wrote:

> Speaking of store files - After really looking into the store logic, it 

The better way to implement the store file (than the old way I did quickly 
use - you have to remember that original store file was just a quick hack 
to concentrate more on SMS side that almost-useless-WAP ;)

 - like earlier, write all messages and acks and nacks to file
 - keep copy of all non-acked messages in memory
 - when Kannel receives an ack (or nack), write a new store file out
   of still remaining (non-acked) messages to replace the old.
   Naturally only do this now and then, like if there has not been writing 
   in last half a minute. (and of course first write to new file and then 
   rename etc.)


..this way the store file normally keeps empty or only some odd messages, 
unless lots of messages do not get (n)acks. Of course this means that
Kannel will grow in memory if messages do not get ackked, too.


-- 
                  &kalle marjola