4 ms·
Maybe ... never use on a congested network. or Never use on a network where congestion is above a certain level or Never us on a network where this parameter
by asdefghyk 2y ago
Maybe ... never use on a congested network.
or Never use on a network where congestion is above a certain level
or Never us on a network where this parameter is above a certain level - like network latency
or only use on a LAN not a WAN ....?
- swiftcoder 2y agoUnless you are building software for a pre-established intranet, how do you predict ahead of time whether your software will run on congested networks? Most end-user software ends up running on a variety of oversubscribed wifi and cell networks
- smcameron 2y ago> how do you predict ahead of time whether your software will run on congested networks? One thing you can do is build in "bad network emulation" into your software, allowing the various pieces to drop packets, delay packets, reorder packets, etc. and make sure it still behaves reasonably with all this garbage turned up.
- asdefghyk 2y agoRE ".... build in "bad network emulation" into your software....." I expect there would be network emulators that would be able to emulate these situations. How good these emulators are would be the next question.
- marcosdumay 2y agoYou tell the user "hey, don't use on congested networks". And yeah, since most internet software has this exact disclaimer, it works kinda well. But people do appreciate software that doesn't have this restriction, and even go out of their way to talk about it (more on mobile networks than on wired connections).
- ot 2y agoLAN can be oversubscribed too, even if your switches have sufficient capacity you can have short packet bursts that fill up the queues. You cannot assume reliable delivery.