------- Additional Comments From [hidden email] 2005-06-05 22:45 -------
(In reply to comment #4)
>> The current implementation is more "accurate" but at the cost of being
> completely intolerant of "slop".
> I could for example, without too much trouble, recode this so that any server
> timestamps that appear to be more than one day in the future be considered last
I have had a go at testing this idea. It breaks our JUnit tests, but that's
just because the JUnit tests were written with a "no-slop" approach. Since I'm
having trouble deciding whether it's a good thing or a bad thing to allow for
"slop", maybe that's a sign that we need a "slop-mode" option in FTPClientConfig
(probably named differently)? Perhaps something similar to how
SimpleDateFormat.isLenient() exists because one size does not fit all?