Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции FTSC_PUBLIC
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 5299 из 7124 ====================================== FTSC_PUBLIC =
От   : Alexey Vissarionov               2:5020/545         19 Dec 20 06:48:00
Кому : Maurice Kinal                                       19 Dec 20 06:48:00
Тема : alternative DateTime (ref: fts-0001.016)
FGHI : area://FTSC_PUBLIC?msgid=2:5020/545+5fdd86aa
На   : area://FTSC_PUBLIC?msgid=1:153/7001+5fdc4e06
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://FTSC_PUBLIC?msgid=30754.ftsc_pub@1:103/705+24433a3e
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001+5fdd8fb6
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001+5fdd9654
Ответ: area://FTSC_PUBLIC?msgid=1:320/219@fidonet+5fdda6c4
Ответ: area://FTSC_PUBLIC?msgid=1:229/426+DD9858EB
==============================================================================
Good ${greeting_time}, Maurice!

18 Dec 2020 06:36:54, you wrote to Andrew Leary:

MK> proposed DateTime = a string 19 bytes long.
MK> Format = "YYYY-MM-DD hh:mm:ss" where,
MK> YYYY = four digit year
MK> MM   = two digit month ranging from 01 to 12
MK> DD   = two digit day ranging from 01 to 31
MK> hh   = two digit hour ranging from 00 to 23
MK> mm   = two digit minute ranging from 00 to 59
MK> ss   = two digit second ranging from 00 to 59
MK> Since there is no room for the UTC offset DateTime should be set to
MK> UTC in order to avoid confusion. This format will ensure that the
MK> packed message is exactly the same byte length as specified in
MK> fts-0001.016 not counting the ASCII null charater that terminates the
MK> string as per packed MSG header specification for all header strings
MK> (eg To, From, subj, etc).

I've only one question: how would the software distinguish that from older (legacy) date format?

Even if we want everyone migrating to the new software, there should be some transition period, while we _must_ (as in FTA-1006) maintain compatibility. Given that, here's my proposal.

The "Date:" kludge containing the date and time in RFC-3339 format with one variation - allow the space between the time and UTC offset. The "datestr" format for that would be "%F %T %:z" (try `date '+%F %T %:z'`).

Rules:
0. The "Date:" kludge _must_ contain valid time in either "%F %T %:z" or "%F %T%:z" format.
1. Once the "Date:" kludge is present in a received message, the compatible software (that's aware of the "Date:" kludge) _must_ use the time from the kludge.
2. When composing a message, the compatible software _must_ fill the "Date:" kludge and _should_ fill the legacy header with the valid time (considering precision limitation) or it _may_ fill the legacy header with all zero bytes.

This would allow us to get rid of ancient software without breakind almost everything.

Also, the example of the "Date:" kludge can be found in this my message :-)


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... god@universe:~ # cvs up && make world
--- /bin/vi
* Origin: ::1 (2:5020/545)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.042568 секунды