i don't know about Catalyst, but basically there are many ways of storing data between processes. the most performant solution would lie in using shared memory. you create the shmem segment in the startup.pl of your application, and any of the app's pages store the common data on it and read from there.
for instance startup.pl might look like (assuming all of the application's global data are stored in a hashtable called %appdata):
use IPC::Shareable ':lock'; [...] no warnings 'untie'; my $knot; my $glue = "SHMEMGLUE"; eval { $knot = tie %tie, 'IPC::Shareable', $appdata{$glue}, { create = +> 0, mode => 0666, size => $appdata{SHMEMSIZE}, exclusive + => 0, destroy => 0 }; }; unless ($@) { $knot->remove; untie %tie; undef $knot; } $knot = tie %tie, 'IPC::Shareable', $appdata{$glue}, { create => 1, mo +de => 0666, size => $appdata{SHMEMSIZE}, exclusive => + 0, destroy => 0 }; untie %tie;
note: this code first tries to find the shmem segment, and if it exists it destroys it. this prevents you from allocating additional memory with each restart of apache.

--------------------------------
masses are the opiate for religion.

In reply to Re: Sitewide states in a web application (specifically cache locking in Catalyst) by TOD
in thread Sitewide states in a web application (specifically cache locking in Catalyst) by Ionitor

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.