There is also great merit in maintaining an index file. You can index, say, the date, title and filename, and the index file will probably remain small enough that you *can* slurp it. I mean, you're not going to run Slashdot with it but even if you post once a day for the next three years you're still looking at a few K. And you can do a few neat tricks like just reading off the top three records to save time.

For great speeedness, use fixed-length records. Space wastage sucks, but you then get the luxury of being able to arbitrarily jump around the file.

<lecture props='grep'>
The thing is, once you you've got a good index file system going, you probably want to add querying abilities, so you'll add in a keyword index. Then you'll break the index handler off into a daemon process so you can update asynchronously and handle collisions. Then you'll generalise the data storage to handle arbitrary data in arbitrary table. You might even add a SQL interpreter. You get the idea - you will thank yourself for learning to use a database and DBI.
</lecture>

But if it's impossible, I meant what I said about an index file.

In reply to Re: Anti-slurp weblog by n3dst4
in thread Anti-slurp weblog by newrisedesigns

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.