in reply to Re^2: Fastest way to store and retrieve configuration information?
in thread Fastest way to store and retrieve configuration information?

The following is of interest:

You can also store data in network order to allow easy sharing across multiple platforms, or when storing on a socket known to be remotely connected. The routines to call have an initial n prefix for network, as in nstore and nstore_fd. At retrieval time, your data will be correctly restored so you don't have to know whether you're restoring from native or network ordered data. Double values are stored stringified to ensure portability as well, at the slight risk of loosing some precision in the last decimals.

so if you use the n prefixed functions the data is serialised in network order so should be fine across architectures.


DWIM is Perl's answer to Gödel
  • Comment on Re^3: Fastest way to store and retrieve configuration information?

Replies are listed 'Best First'.
Re^4: Fastest way to store and retrieve configuration information?
by Booger (Pilgrim) on Nov 30, 2005 at 20:39 UTC
    Guess I should have RTFM a little more, eh?

    Thanks again!