My coworkers have not used Perl. They are not biased against it, but they do have many of the common misconceptions. However, we recently found ourselves in a situation where for our new document management system, hosted on Apache+JBoss, we needed a way to handle file downloads. I was told that this had to be implemented with a Servlet in JBoss because the access control system required calling some database procedures, but there was much fretting over the use of a servlet for the actual file downloads because some of the files are big.
So I said, "well, why not let Apache handle the downloads." And they said, "well what about access control." So I said, "why not write a mod_perl authentication handler for the access check and an output filter to deal with the fact that the files are locally encrypted" and they were intrigued. Now, of course, the challenge is that I need to give them some actual code :)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
