> I'd like to depracate
> remove(MailImpl)
> remove(String)
> And replace them with remove(collection<MailImpl>)
There are sufficient cases where single remove is natural in the API. I'd
sooner deprecate remove(String), and eventually make it private. But that's
not practical, yet, either. In order to get a message, you either use
Spool.accept() or MailRepository.list(). The latter provides a
List<String>.Iterator.
The worst sequence is this one:
String key = spool.accept();
MailImpl mail = spool.retrieve(key);
which leads to all sorts of cruft and problems, such as the locking. I'm
not sure why it wasn't:
MailImpl mail = spool.accept([delayTime]);
That is a change I'd like made.
Fortunately, none of these classes are part of the Mailet API, and I'd like
to keep it that way until they are cleaned up.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
