| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Protocol Flags |
> jh>How is it caller-driven? The receiving system will pick > the > jh>protocol it prefers, from the list presented by the > calling > jh>system. > Isn't this logic backward, Joho? Shouldn't the caller, who's > probably paying for the transfer, get the right to make the > decision as to which protocol is used? If it's up to the calling system, and it doesn't know what the receiver's capabilities are, you end up with a potential "No compatible protocols" situation far more frequently than today. Logic (I know that doesn't usually apply :-) dictates that software would at least know that Zmodem is somewhat more efficient than Xmodem :-) > In other words, shouldn't the receiver present its list of > supported protocols and shouldn't the sender reply to that > with the one it wants? Probably - but that requires an additional turn-around. You can't simply switch the handshake sequence because in some cases, it is not desireable for the receiver to "show itself" until it knows who's calling. ---* Origin: Absolute Solutions (2:270/17.6) SEEN-BY: 50/99 54/54 102/2 112/1 132/888 170/400 209/720 270/101 280/1 5 66 SEEN-BY: 280/77 333 290/627 357/1 396/1 620/243 632/348 640/201 206 217 297 SEEN-BY: 640/305 316 556 820 821 822 823 690/660 711/409 410 413 430 431 454 SEEN-BY: 711/807 808 809 816 929 934 938 942 712/623 713/888 800/1 3615/50 @PATH: 270/17 24/24 396/1 280/1 209/720 640/820 711/409 54/54 711/808 809 934 |
|
| 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™.