Changes between Initial Version and Version 1 of Ticket #134


Ignore:
Timestamp:
Apr 4, 2020, 7:45:19 PM (11 months ago)
Author:
schwa
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #134 – Description

    initial v1  
    55- Having a server use UTC for its timestamps makes sense because using a timezone may lead to skipped or double hours for daylight saving time switches. So I think the assumption is justified anyway that most servers will use UTC.
    66
    7 Therefore, ftputil should assume the server uses UTC in listings. Of course, this assumption may be wrong, but in that case there's still the time shift concept (local server time minus local client time). If the server time in listings is ''actually'' UTC, the time shift is zero (see also next paragraph). The server doesn't use UTC, a time shift can still be set with `FTPHost.set_time_shift`.
     7Therefore, ftputil should assume the server uses UTC in listings. Of course, this assumption may be wrong, but in that case there's still the time shift concept (local server time minus local client time). If the server time in listings is ''actually'' UTC, the time shift is zero (see also next paragraph). If the server doesn't use UTC, a time shift can still be set with `FTPHost.set_time_shift`.
    88
    99On a related note, `os.path.getmtime` [https://docs.python.org/3/library/os.path.html?highlight=getmtime#os.path.getmtime returns the time as seconds since the epoch] (i. e. UTC), so comparing (UTC) timestamps from the server and the client become trivial, apart from the precision of the server times.