On torsdag, mar 20, 2003, at 19:01 Europe/Stockholm, Alan Barclay wrote:
Digest::HashCash doesn't seem to be a good place, because it's
not performing a digest
Crypt::HashCash same problem, it's not doing crypto
Mail::HashCash would work, except I can see non-mail releated uses.
Hash::HashCash
On Mar 20, Alan Barclay wrote:
> I've just finished a module which allows users to generate and
> validate hashcash tokens.
>
> Hashcash tokens are bitstreams which are hard to calculate, but
> easy to verify, and are therefore proof that the generator
> performed a certain amount of CPU work, an
> On Thu, 2 May 2002 20:59:51 +0100, Pete Barlow <[EMAIL PROTECTED]> said:
> Hi,
> I've developed a module for use in my genealogy/family history
> work. It provides a custom user dictionary for surnames/lastnames
> with the ability to add, delete, search for names. The purpose
> is
[EMAIL PROTECTED] (Karthik Krishnamurthy) writes:
> I am coding a suite of modules for parsing and manipulating
> various Unix system configuration files. I had in an earlier mail
> asked for advice on the name to use. I had stated my preference for
> the 'Nix' toplevel namespace, as I alrea
Mail::Header::Received is probably not a good place for it given
that Mail::Header is a bit different.
However If you module could be made to work with Mail::Field then
that would be great. Parsing of mail headers is exactly what
that package is all about.
Graham.
On Sun, Mar 19, 2000 at 10:28:
