First, I agree fully with the part about handicap access, and I think that it should be a show stopper for any moral programmer; even one getting paid for doing such work.

Second, stringing together images is a bad idea, because you can look at the image names and (presumably) the bot can just translate the image tags to the words. Simple obfuscation might not work. My own preference for a module to do all graphics stuff is Gimp/Perl. The Perl-Server that comes with this moves the graphics processing into a seperate process from the webserver, so you only have the glue in all the apache (or ...) processes. Note however that the locking doesn't work in all versions, so I just flock() a lockfile.


--
Snazzy tagline here

In reply to Re^2: Stop Form Hurling by Aighearach
in thread Stop Form Hurling by awohld

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.