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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 2319 из 7124 ====================================== FTSC_PUBLIC =
От   : Michiel van der Vlist            2:280/5555         31 Jan 17 15:11:05
Кому : Nicholas Boel                                       31 Jan 17 15:11:05
Тема : FSP-1040.001 Draft #3
FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+58909eac
На   : area://FTSC_PUBLIC?msgid=1:154/10+588fab99
= Кодировка сообщения определена как: CP850 ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.73+5893bbcc
==============================================================================
Hello Nicholas,

On Monday January 30 2017 15:04, you wrote to Kees van Eeten:

KE>> I think you are documenting common practice in FTN or only
KE>> Fidonet.

NB> Why not cover both when you can?

Because:

o It is not our job. Fidonet is Fidonet and the Internet is the Internet.
  The FTSC documents Fidonet. Period.

o Mixing Fidonet en Internet specs is confusing. The 00-24 for the hours
  illustrates that. "24" may be valid for some applications in the Internet,
  it definitely is not valid in Fidonet.
  FTSC docs should not try to document everything. They should be a guide to
  programmers saying: "if you do it like this, it will work."

NB> Since there is plenty of Fidonet software that integrates Fidonet
NB> with the internet.

Actually there is few "Fidonet software" that "integrates" Fidonet with the Internet. Yes, Fidonet uses the InterNet as a transport medium. It uses the InterNet to transport files from one node to another. But it does not /integrate/ with it.


KE>> Programmers are stubborn people with strong opinions on how
KE>> things should be done. The documentation should keep them at bay
KE>> to ensure interconnectivity.

NB> The programmers are the ones creating current practice. Nothing is
NB> keeping them at bay at all. We follow their lead and document what
NB> they do as "current practice". Not the other way around.

It is an interaction, not a one way street. Once current practise has been documented as a guide to programmers - "if you do it like this, it will work",  they are implicitly told "if you are stubborn and do it different, in a way that conflicts with the standard, it will probably not work and your efforts will be wasted".


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: http://www.vlist.org (2:280/5555)

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