| |||||||||||||
|
| |||||||||||||
Networking change causes distribution headachesNetworking change causes distribution headachesPosted Oct 29, 2008 4:31 UTC (Wed) by jamesh (subscriber, #1159)In reply to: Networking change causes distribution headaches by PaulWay Parent article: Networking change causes distribution headaches
In this particular case, there are multiple ways to structure a packet that are considered equally valid according to the RFC and have the same code complexity.
One of the options happens to avoid a bug in certain hardware, probably due to matching the behaviour of a certain competing operating system. Why on earth wouldn't you choose that option?
Your suggestion would result in more complex code that has the potential to be slower and more buggy.
(Log in to post comments)
Networking change causes distribution headaches Posted Oct 30, 2008 7:00 UTC (Thu) by grahammm (guest, #773) [Link]
So what happens when (as is sure to happen some time) option A is needed to avoid a bug in one particular hardware and option B to avoid a bug in a different hardware?
Networking change causes distribution headaches Posted Oct 30, 2008 14:44 UTC (Thu) by mrshiny (subscriber, #4266) [Link]
Worry about that when it happens. Until then, zero-cost workarounds that prevent loss of functionality are more desirable than some sort of notion of purity.
|
|
||||||||||||