Timo -
Consider me puzzled. There is something missing in the spec for this
project - what is the developer trying to do, simply get the log files?
If so then rsync, wget, or scp from the commandline, or a gui-based scp
tool seem much more useful than any sort of programming solution.
Ok, so barring that, I think this seems a perfect use of a scripting
language - either perl or any of the various *sh variants. Perl will give
you handy, high-level file processing features that will allow the script
to zip through a file (even in a .tgz) with very little coding. *sh
variants will have similar chunky, high-level features (between tar,
find, grep and ls and a few pipes I think there is a simple solution).
Either can be readily incorporated into Apache, and with a slight bit
more trouble, into your favorite servlet container or (god forbid) IIS.
So really the question becomes, what is the developer comfortable with?
In terms of professional development I'd say everyone should have some
scripting language under their belt. If the fellow has to depend on Java
to do the task I'd hazzard to guess he'll spend 3-4 times longer on the
solution. If that is the soultion he has to fall back on, send him home
with a copy of the Larry Wall Perl book (O'Reilly Press - wtf's the name?
Perl in a Nutshell?), or a printout of 'man bash' (though this assumes
he has some facility with the cadre of shell commands he'll need - cat,
grep, find, tar, ls, ...) and tell him to grind on the solution a bit
longer than he would have in order to get the script going in scripting
language. Dollars to doughnuts, I bet it pays off in time savings the
next time he's confronted with a data crunching task.
-Duffy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
