I have another solution. Keeping images, maybe large ones,
in memory or in a database forces you to use mod_perl to
deliver them: you have a long print that can be instead
handled by apache itself. You are replicating content
generation and embedding security inside this phase of
apache's life cycle.
What you need instead is authentication, authorization
and access control. Following this route you need 'only' to
create directories with access rights embedded in their
names. A dedicated access control can give authorization
to display some content to the real apache, gaining in
speed and modularity.
If you need to share images between many servers I think
NFS fyle system is a better option. Some discussions about
this option can be found on mod_perl mailing list.
Hope this helps. Ciao, Valerio
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||