Theo Van Dinter writes:
> Justin,
>
> While I was perusing the ArchiveIterator code, wherein I plan to make a bunch
> of changes, I noticed (via svn blame):
>
> 418043 jm if ($self->{opt_j} < 2) {
>
> in the section which is figuring out single vs multiple process in run().
> However, this line makes opt_j < 2 run in a single process, as opposed
> to the original/documented behavior which was to run that section only
> when opt_j == 0.
>
> What was the change for?
Well, opt_j == 1 means "run 1 job simultaneously", ie. use a single
process for mass-check. That's the same as opt_j == 0, ie. use
a single process for mass-check.
However I now note that actually the POD docs for ArchiveIterator
explicitly describe two different behaviours for opt_j == 1 vs
opt_j == 0! So my change was an error. oops. ;)
--j.
> ------------------------------------------------------------------------
> r418043 | jm | 2006-06-29 09:36:04 -0400 (Thu, 29 Jun 2006) | 1 line
>
> preflight: no longer builds a link farm for mass-checks - instead let
> mass-check itself do the hard work, but support this with more caching and
> smarter message-selection algorithm
> ------------------------------------------------------------------------
>
>
> --
> Randomly Generated Tagline:
> "DAKA ... for a good night of fasting." - Theo
