Comment for future possibility.

This commit is contained in:
wb2osz 2017-12-16 10:03:30 -05:00
parent f7742cf044
commit 22c810e442
2 changed files with 10 additions and 2 deletions

View File

@ -484,6 +484,16 @@ static packet_t digipeat_match (int from_chan, packet_t pp, char *mycall_rec, ch
break; break;
} }
// Idea: Here is an interesting idea for a new option. REORDER?
// The preemptive digipeater could move its call after the (formerly) last used digi field
// and preserve all the unused fields after that. The list of used addresses would
// accurately record the journey taken by the packet.
// https://groups.yahoo.com/neo/groups/aprsisce/conversations/topics/31935
// > I was wishing for a non-marking preemptive digipeat so that the original packet would be left intact
// > or maybe something like WIDE1-1,WIDE2-1,KJ4OVQ-9 becoming KJ4OVQ-9*,WIDE1-1,WIDE2-1.
return (result); return (result);
} }
} }

View File

@ -38,8 +38,6 @@ struct digi_config_s {
enum preempt_e { PREEMPT_OFF, PREEMPT_DROP, PREEMPT_MARK, PREEMPT_TRACE } preempt[MAX_CHANS][MAX_CHANS]; enum preempt_e { PREEMPT_OFF, PREEMPT_DROP, PREEMPT_MARK, PREEMPT_TRACE } preempt[MAX_CHANS][MAX_CHANS];
//char type_filter[MAX_CHANS][MAX_CHANS][20]; // TODO1.2: remove this
char *filter_str[MAX_CHANS+1][MAX_CHANS+1]; char *filter_str[MAX_CHANS+1][MAX_CHANS+1];
// NULL or optional Packet Filter strings such as "t/m". // NULL or optional Packet Filter strings such as "t/m".
// Notice the size of arrays is one larger than normal. // Notice the size of arrays is one larger than normal.