Have they mentioned yet how fast the java solution is? And how many LOC? Is it even done yet :) ?? Without knowing what data is typical, there's no way to tell which solution is best. Your first solution is the simplest and safest without knowing what the data is (and like you said, it would've been done by now anyway). The FileCache mentioned earlier or your hash solution might be the best depending on the data. But don't be too disappointed if they don't listen and think perl is "too slow" and don't realize that perl (or some other "scripting language") would've been perfect for this. Also, if they are too perl-inexperienced (and/or java-centric) to realize this, then any perl solution is unmaintainable to them.
-
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.
|
