Storing the file signatures should be easy to add, as I will
most likely add a stringification routine to the File::Signature
class; retrieving the signatures from a file would then mean parsing
the file back in - something which would get nasty with weird filenames -
here, either a small DBMS or a tied DB would be necessary to store the data,
not nice, but feasible.
Getting the difference between two signatures does not
always have a meaning, for example the difference between
two MD5 checksums. I could add the method to always
store the timestamps, but timestamps are not always
something you want to rely on - I'm thinking about NFS mounts
with jumping clock times. A method to tell the time since the
last update to the file-database is a responsibility of the
main program and not of the module.
perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The
$d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider
($c = $d->accept())->get_request(); $c->send_response( new #in the
HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web
-
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.
|