[aprssig] Preliminary delayed packet analysis
AE5PL Lists HamLists at ametx.comSat Jun 17 23:14:56 UTC 2006
- Previous message: [aprssig] Dead Reckoning in APRS
- Next message: [aprssig] APRS and Field Day question...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: Keith - VE7GDH > Posted At: Saturday, June 17, 2006 3:56 PM > Subject: RE: [aprssig] Preliminary delayed packet analysis > > and pin down where the delays are happening. So... while not > suggesting dupe checks for 24 hours, what would be involved > in changing it from 30 seconds to a minute or two? Would it > take a lot of extra horsepower to do it? Of course, as you > say, it would just be masking the problem instead of fixing it! This is not a question of "horsepower". As I stated before, it is a question of what breaks when you do this (like messaging). It is also a question of getting 400+ sysops to do make this change (I have no idea if aprsD even has this as an option). So, IMO it is not worth the effort simply to mask the problems (and make them harder to diagnose) especially when you will introduce new problems with this "fix". 73, Pete Loveall AE5PL mailto:pete at ae5pl.net
- Previous message: [aprssig] Dead Reckoning in APRS
- Next message: [aprssig] APRS and Field Day question...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
