MSGID:  bca5a1e5
REPLY:  990e9675
PID: PyGate 1.5.2
TID: PyGate/Linux 1.5.2
CHRS: ASCII 1
TZUTC: 1100
REPLYADDR c186282@nnada.net
REPLYTO 3:633/10 UUCP
On 12/12/25 06:41, Andy Burns wrote:
> The Natural Philosopher wrote:
> 
>> Well the daemon runs under xinetd...for sheer laziness. I guess I 
>> could make it UDP.
>>
>> But I don't know what problem that would solve.
> 
> The data would arrive if a single packet got through the fog, whereas 
> with tcp at least dour packets on sequence need to make it (or get 
> retried) with UDP you could afford to spray each packet half a dozen 
> times and if one of them makes it, you're good ...

   I once made a bi-directional client/server setup,
   first Python, then 'C'. One variant was TCP, the
   other UDP. Probably could have used a config file
   or defs ... but I never got to it.

   On a clean LAN, both worked perfectly. However
   with some outdoor devices (Pi2 + wifi dongle as
   best I recall) both approaches had issues kind
   of similar to what you described.

   TCP, while "error resistant", was often VERY iffy.
   UDP - well - easier/smaller to send. You could
   scan each packet for obvious errors and, if a
   fail, could ask for it again or just let the
   pgm work around to sending that data again.

   For almost all modern apps, TCP is best by far.
   However iffy situations CAN still exist, so
   UDP you add some IQ to MIGHT be better.

   As I've said elsewhere, wifi can sometimes be
   black magic. Weird RF shadows and multipaths
   can be anywhere and it's very hard to tell
   what's perfect placement.

   Hmm ... apparently CANbus can be sent over
   wifi - but you lose some error-checking so
   there's no gain. There are various dongles
   for lower-freq data transmission too, but
   never got around to trying them. Fidelity
   might be worth losing some speed.


--- PyGate Linux v1.5.2
 * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 112 134 200 206 275 300 317 400 426
SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219
SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422
SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35
PATH: 633/10 280 229/426