Re:Lessons from Ancient File Systems
by jclulow on Monday July 29, 2024 @10:58PM
(#41105706)
Seems like a lost opportunity to introduce 0xFF as the error code that means "look in the extended error field we've since added to the message, which includes a u32 _and_ a human readable string for display" to be honest.
[ Parent
| on HN ]
Re:Lessons from Ancient File Systems
by didgetmaster on Tuesday July 30, 2024 @01:04PM
(#41111480)
It's been many years ago; but if memory serves...the error code was part of a header in a server response packet. Expanding that header to include another field would break all the clients and handler software.
Eventually, a major release fixed the problem with a different header with expanded fields; but that was not a simple fix. Like I said, backwards compatibility CAN be the bane of innovation.