| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Packet type 2+ |
-=> Quoting Goran Eriksson to All <=- GE> Note 1 GE> There is a potential conflict between packet type 2+ and programmes GE> not recognizing that packet type regarding the product code. GE> Since the product code in packet type 2 is only an 8-bit unsigned GE> integer while it is in packet type 2+ is a 16-bit unsigned integer, GE> programmes not recognizing incoming incoming packets of packet type 2+ GE> may not recognize the complete 16-bit product code. GE> Normally this is a minor problem since programmes not recognizing GE> incoming packets of packet type 2+ will usually only use this GE> information for logging and similar purposes, if at all. Except that there are programs that compensate for buggy packet formats produced by some mailers by reading the packet code. GE> To further ease this problem, it is the current practice of the FTSC GE> to assign only product codes with FFH as the low order byte (i.e. GE> product codes 01FFH, 02FFH, 03FFH, ... FFFFH). A programme only GE> recognizing incoming packets of packet type 2 will then interpret the GE> product code as FFH which is a reserved 8-bit product code for GE> programmes with 16-bit product codes. --- Blue Wave/DOS v2.30* Origin: Shadowshack (1:105/51) SEEN-BY: 201/0 100 200 209 300 400 407 411 505 600 203/600 204/450 700 205/0 SEEN-BY: 206/0 270/101 490/21 633/267 270 @PATH: 105/51 360 138/146 270/101 201/505 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.