Re: persistent name server option coming in 4.30

Morten Lind <[email protected]> Fri, 7 Nov 2014 08:49:22 +0100
Newsgroups gmane.comp.python.pyro
Organization SINTEF Manufacturing
Message-ID <1898793.6AO05mfIz6@mly13>
Very nice! I have considered this myself, and would have used MongoDB for it. Maybe you could throw that in as an option?

Vennligst / Best regards,
Morten Lind
Senior Researcher
Dept. of Production Technology
SINTEF Raufoss Manufacturing
Mobile: +47 9266 2194

On Thursday 6. (45) November 2014  22.36.27 Irmen de Jong wrote:

> Hi,
> 
> For the next version I've started to add a persistency feature to the name server.
> It's starting to take shape pretty well I think, I've just committed stuff that adds a
> '-s' (storage) option to the name server where you can select the storage type to use.
> Default is still the volatile in-memory storage, but you can also specify
> "dbm:nameserver.dbm" to let the nameserver store its registry in a persistent dbm
> datafile on disk. Next time you run the nameserver it will remember all registrations :)
> I'm planning on adding a sqlite based storage option as well because the dbm one doesn't
> scale (dbm doesn't allow concurrent access).
> 
> 
> Irmen
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyro-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pyro-core

------------------------------------------------------------------------------