| |
PA2AGA > HDDIG 02.11.99 01:38l 188 Lines 6073 Bytes #-9698 (0) @ EU
BID : HD_99_278C
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/278C
Path: DB0AAB<DB0ZKA<DB0LX<DB0LEL<DB0TTM<DB0FP<DB0SRS<DB0ZDF<DB0AIS<DB0NDK<
DB0ACH<DB0ACC<PI8DRS<PI8ZWL<PI8APD<PI8WNO<PI8HGL<PE1NMB<EA7URC<PE0MAR<
PI8VNW
Sent: 991101/1948Z @:PI8VNW.#ZH2.NLD.EU #:12245 [HvHolland] FBB7.00g $:HD_99_27
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA22380 ; Mon, 01 Nov 99 19:17:47 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016697 ; Mon, 01 Nov 99 19:16:34 MET
Date: Mon, 01 Nov 99 19:13:57 MET
Message-Id: <hd_99_278C>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/278C
X-BBS-Msg-Type: B
be incomplete. Thus, if a protocol specification defines four
possible error codes, the software must not break when a fifth
code shows up. An undefined code might be logged (see below),
but it must not cause a failure.
The second part of the principle is almost as important:
software on other hosts may contain deficiencies that make it
unwise to exploit legal but obscure protocol features. It is
unwise to stray far from the obvious and simple, lest untoward
effects result elsewhere. A corollary of this is "watch out
for misbehaving hosts"; host software should be prepared, not
just to survive other misbehaving hosts, but also to cooperate
to limit the amount of disruption such hosts can cause to the
shared communication facility.
--
... Hank
http://horedson.home.att.net
Ian Wade <ian@dowrmain.demon.co.uk> wrote in message
news:McgDk$AmTIH4EwBC@dowrmain.demon.co.uk...
> Somewhere in the 2000-odd RFCs there's a statement that goes something
> like "When implementing a protocol, be strict about what you send but
> liberal about what you receive."
>
> Can someone point me to chapter and verse, as I want to quote this in a
> document I'm writing.
>
> Thanks.
>
> 73
> Ian, G3NRW
> --
> +-----------------------------------------------------------------+
> | APRS on 144.800 [IO91SX] ~55km/35 miles NNW of London |
> | email: g3nrw@arrl.net |
> | |
> | INTRODUCTION TO APRS: http://www.netro.co.uk/whitepaper.htm |
> | APRS PROTOCOL SPEC: http://www.tapr.org/tapr/html/aprswg.html |
> +-----------------------------------------------------------------+
>.
------------------------------
Date: Sun, 31 Oct 1999 12:34:00 -0800
From: "Hank Oredson" <horedson@att.net>
Subject: Help with RFC
Any time ... (smile).
Bunch of RFCs lurking on this machine, so simple search
through the text found that one, and also RFC-1123.
Have used that quote many times ... is a good one.
--
... Hank
http://horedson.home.att.net
Ian Wade <ian@dowrmain.demon.co.uk> wrote in message
news:KtASoHCl7JH4EwTB@dowrmain.demon.co.uk...
> In article <7vi1qq$cee$1@bgtnsc02.worldnet.att.net>, Hank Oredson
> <horedson@att.net> writes
> >One place it is quoted is RFC-1122:
>
>
> Thanks Hank. That's exactly what I was looking for.
>
> 73
> Ian, G3NRW
> --
> +-----------------------------------------------------------------+
> | APRS on 144.800 [IO91SX] ~55km/35 miles NNW of London |
> | email: g3nrw@arrl.net |
> | |
> | INTRODUCTION TO APRS: http://www.netro.co.uk/whitepaper.htm |
> | APRS PROTOCOL SPEC: http://www.tapr.org/tapr/html/aprswg.html |
> +-----------------------------------------------------------------+
>.
------------------------------
Date: Sun, 31 Oct 1999 21:11:55 -0600
From: "Earl Claus" <santa@theshop.net>
Subject: Packet for Palm Pilot ?
The question was about Palm Pilot sotware, not Windows CE software. As you
gentlemen know, Windows CE software will not work on a Palm Pilot.
Peter,
To answer your question...
Look toward any of the Palm 3 or Palm Pilot web sites for a VT100 terminal
emulator (www.markspace.com). I take it that you found out that the card
edge on the palm pilot is really an RS232 interface. A standard palm 3 to
PC serial cable purchased from an office supply shop should work with any
standard 9 pin din connector TNC.
Good Luck, Peter!
"Claus Peter Neff" <peter@neffworld.de> wrote in message
news:7v4uqr$mh9$1@news04.btx.dtag.de...
> Hi,
> I am searching packet radio software to connect my Palm Pilot to a tnc -
this
> would allow me to work with a realy portable station...
> 73
> Peter
> DL4ZAQ
>
> e-mail: peter@neffworld.de
>.
------------------------------
Date: Thu, 28 Oct 1999 14:49:22 GMT
From: 106255.1565@CompuServe.COM (RF)
Subject: PACTOR or AMTOR
Bob Lewis <aa4pb@erols.com> wrote:
>
>Icom charges for their rigs - where's the hamradio spirit in that... I
>guess anyone who designs and builds a product (whether hardware or
>software) has the right to give it away or to ask to be paid for it. I
>think they learned a lesson from Pactor-I where many mfgs. sold hardware
A charge is to be made for the use of the 'Morse code' by amateur
radio operators. This will be backdated to 1st. January 1900. All
past and present users of the mode should therefore apply for a
licence number together with their payment for past and future use.
>.
------------------------------
Date: Thu, 28 Oct 1999 14:35:00 GMT
From: 106255.1565@CompuServe.COM (Richard C. Ferryman)
Subject: What Pactor / packet foftware to handle PK-232 and TNC2 clone
I have tried XPWIN and a couple of other apps but am looking for
software to handle two or more TNCs one of which is a PK-232/DSP in
Pactor fot HF and the other a TNC2 clone for VHF. Winlink looks great
but may be overkill. Any suggestions. My needs are:
1. Handling PMS mail and auto retrieving from VHF/HF sources.
2, Must handle the above hardware
3. Would be an advantage if a Pactor login could cross connect to the
local VHF packet system.
Software comes and goes and I may have missed some new versions.
Richard G4BBH
>.
------------------------------
End of Ham-Digital Digest V99 #278
******************************
You can send in your contribution to this digest by
sending an e-mail to: hd-group@pa2aga.ampr.org
or (via BBS-net) to: hdaga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
