If the application/library requires Internet access to work properly, I'd store it server side. I mean if net access is needed, will the data be of any use sitting on the client if there is no access? A DB sounds like the best bet, and server side means no software needs to be installed on the client.

If you want to keep it client side and are going to serialize it instead of using a DB, I'd go with JSON over Storable. It's cross-platform, you don't need to worry about conflicts in the version of Storable, and it's human-readable/editable with a text editor. It's also a lot easier to fix a corrupt JSON file than it is a Storable one.

In reply to Re: Persistent data by stevieb
in thread Persistent data by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.