Mike Coslo wrote:

...
This is a presumed frequency agile system that won't interfere with other
signals already on the band. If it works, one possible outcome is that no
available frequency will be found, and no connection made. Failure is a
built in option!

- 73 de Mike N3LI -


Sorry, in my haste I missed making a suitable response to this part of
your post.

I never see a "failure", so to speak, occurring (other than catastrophic
failure and requiring repair of hardware/firmware/software.) And, under
peak-loads/hardware-failure/etc., slowdowns may occur. However, this
would happen to any/all net traffic under adverse condition. Indeed,
you really don't know how the net gets to you,
satellite/hard-line/cell-tower/etc. are all being implemented behind the
curtains and simply ends up looking seamless to us, the users.

The net should not be viewed as a long winded amateur who abuses "key
down" time. The net is in packets, these packets are of a sensible size
and sent "in turn." There are rules to prevent one or more "glutton(s)"
from being able to adversely affect net traffic.

From my home wifi router/switch to the data streams off a major
backbone, packets are handled this way. Usually some type of
First-In-First-Out (or, FIFO) queue is implemented (packets may not
always be transmitted "in order", however, they will always carry an id
which allows the logical data stream to reconstructed.) Your packet is
never "lost" or "ignored", it is simply "waiting in line", like a busy
supermarket--your "shopping time" may vary.

Regards,
JS