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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 4034 из 7124 ====================================== FTSC_PUBLIC =
От   : Markus Reschke                   2:240/1661         06 Dec 18 19:44:42
Кому : Fred Riccio                                         06 Dec 18 19:44:42
Тема : FTS-5001
FGHI : area://FTSC_PUBLIC?msgid=2:240/1661+5bfd8f72
На   : area://FTSC_PUBLIC?msgid=1:132/174+5c0923dd
= Кодировка сообщения определена как: LATIN1 =================================
Ответ: area://FTSC_PUBLIC?msgid=1:132/174+5c093da2
Ответ: area://FTSC_PUBLIC?msgid=2:280/5555+5c098a26
Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d46cb
==============================================================================
Hello Fred!

Dec 06 13:06 2018, Fred Riccio wrote to Markus Reschke:

MR>> How do we resolve this dilemma?

FR> FTSC needs to document current practice.

Which one? ;) Now we have two, partly contradicting.

MR>> If all entries for Z1 nodes follow the
MR>> undocumented feature then I could add a special case to my tool to
MR>> take also the addresses listed in the INA flag.

FR> Good luck getting ALL nodes to do anything.  Why only zone 1?  It
FR> should apply to all FTN networks and zones.

I agree that we should have one standard for all nodes. But we have two now and have to figure how to merge them into one.

MR>> The frustating thing is that it's hard for software developers to
MR>> know about undocumented features.

FR> Proper testing should uncover current practice.  When you wrote your
FR> tool, did you check it against BinkD.Txt (with diff, FC, or a similar
FR> tool) to see if it was generating the same data file?  How many
FR> NodeLists did you compare?

I did comparisons with the output of other tools. The funny thing was that my tool extracted more binkp nodes. There are nodes with addresses hidden in the system name or telephone number, the DO4 user flag and more. Besides checking the FTSC docs I had to figure out what else is hidden in the nodelist.

MR>> Please tell the FTSC about such stuff, so we are able to
MR>> document that.

FR> Ummm...  I think I just did.  With EchoMail to the FTSC chair in a
FR> public echo conference.  It even got the attention of an FTSC member
FR> (you).  The ball is in your court.

First we have to get all the details of the undocumented standard. How are port numbers handled? If we take Carol's nodelist entry as example and assume she runs binkd on port 8080 we would have:

  INA:shenks.synchro.net,IBN:shenks.dyndns.org:8080

Does the port 8080 also apply to shenks.synchro.net? Or is the standard binkp port assumed for shenks.synchro.net?

FR> FYI, I agree that using two IBN records, as documented in FTS-5001,
FR> would have been a LOT cleaner than one INA and one IBN, but one of
FR> each DOES work.  To quote a past FTSC chair, "If you do it this way,
FR> it will work".

Contradicting standards aren't very helpful.

ciao,
Markus

---
* Origin: *** theca tabellaria *** (2:240/1661)

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