If o/s supports fifos, then they are better than using a database, e.g. 
package persque;
sub new {
    bless { FIFO => shift()}; # must be given an existent fifo file or
+ creatable filename
}

sub install { # create persistent queue
    my $self = shift;
    mkfifo $self -> { FIFO }
      or die "$!: " . $self -> { FIFO } . "\n";
}
    
sub enqueue {
    my $self = shift;
    my @items = @_;
    chomp @items;
    open $fh, '>' . $self -> { FIFO }
      or die "$!: " . $self -> { FIFO } . "\n";
    print $fh (map { $_ . "\n" } @_);
    close $fh;
}

sub dequeue {
    my $self = shift;
    open $fh, $self -> { FIFO }
      or die "$!: " . $self -> { FIFO } . "\n";
    my $r = <$fh>;
    close $fh;
    $r;
}
1;

[download]

One world, one people

In reply to Re: Data::Queue::Persistence experience by anonymized user 468275
in thread Data::Queue::Persistence experience by Anonymous Monk

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.