In my work application there are 3 singleton classes.

The first is the CGI object, which inherits from the (non-singleton) 'site' object (the configuration of this installation of the app), and adds to it the CGI-specific I/O capabilities. It is created at BEGIN time and stored in a lexical variable at the package scope to ensure its singularity.

The second is the logging object, which captures most stderr output and splits it to a per-script, per-site logfile. It is created when needed (though at BEGIN time in the case of a CGI invocation), and stored in a lexical variable at the package scope to ensure its singularity. Arguably it should not be - certain scripts need to deal with information from multiple sites - but I haven't yet worked out what correct behaviour really is in such cases, and current behaviour hasn't proved a problem to date.

The third is arguably not a singleton: it is the database class that mediates access to the 'site' table, containing the client-modifiable configuration options. This uses our base database abstraction layer, but overrides the insert/delete mechanisms to ensure that the given site has only one entry in the table.

None of these are serialised per se, except in the sense that the fields of the last one are serialised to store them in the database.

Hope this is of some use as a data point,

Hugo

In reply to Re: Storable singletons by hv
in thread Storable singletons by xdg

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.