The greylist daemon I wrote (http://www.x-grey.com/ http://www.x-grey.com/) keeps everything in memory, with a checkpoint (everything gets written out to disk)

The greylist daemon I wrote (http://www.x-grey.com/ http://www.x-grey.com/) keeps everything in memory, with a checkpoint (everything gets written out to disk) every hour (the main process forks, and it's the child that does the writing). A similar approach might be applicable here. It could very well be a RAM based approach might be viable once memristros (http://en.wikipedia.org/wiki/Memristor#Potential_applications http://en.wikipedia.org/wiki/Memristor#Potential_application...) are used for memory.