I wasn't involved in the design decision, but I would say a long is by
far the simplest, smallest in memory and most flexible way of
returning a time stamp. The util.date is bug-ridden, complicated,
inflexible (90% of the api is deprecated) and unnecessarily confusing
with e.g. the zero-based months and the odd interaction with Calendar,
(default) Locale, and (default) TimeZone, all of which are irrelevant
to time-stamping a resource.
On 10/8/08, Andrea Francia <[EMAIL PROTECTED]> wrote:
> The FtpFile#getLastModified() method returns a long, why not a
> java.util.Date?
>
> public interface FtpFile {
>
> /**
> * Get last modified time.
> */
> long getLastModified();
> }
>
> The behavior is not specified in the case the file does not exists.
>
> --
> Andrea Francia
> http://andreafrancia.blogspot.com/2008/07/colinux-linux-dentro-windows.html
>
>
