I got nothing against otters.
They're cute, playful, inquisitive, and so on. We should take joy in their simple life, and protect their habitat.
Neither they nor their human analogues, however, should be allowed to design software.
When you're porting a large software system from one platform to another you spend a lot of time dealing with the design and implementation..uh..quirks of the original builders. Sometimes it's just stylistic stuff like typedef'ing (C) or renaming (Ada) every single freakin' standard type name. Other times, though, you'd swear that otters had been tasked with coming up with the design.
So the part I'm porting now has a central control process and a GUI process that communicates via sockets. All well and fine.
The latest issue I've been dealing with has to do with the operator clicking on a field in a table to change it, which pops up a menu of valid entries, one of which is selected and then the "Done" button is clicked. Somewhere, though, in the update processing chain the value was getting trashed, causing the update to fail.
In other words, run-of-the-mill porting issues.
So I traced through the code and verified that the operator's selection was getting properly packaged up into a message and sent out through the socket. I followed it right up to the socket write, so there was no doubt.
I then went to the recipient of the message, the central control process, and verified that the message was being properly received and decoded.
The next thing that's done after receiving the message is calling a function called Update_Table(). The invalid data error is being detected inside this function. However, the data from the message I just read in is not being passed into Update_Table. WTF? Why is it failing then?
So I dig down into Update_Table and see that what it's doing is going out to query for the data in the table row that's about to be updated. But it's not getting this data from a database. Nor is it accessing some internal data structure model. It's sending out a message.
To the GUI process.
And so now I go back to the GUI process and start tracing from where that message is received. So is the GUI process maintaining some data store itself that it maintains and both displays to the operator and keeps for queries from the controlling process? Why, no, no it doesn't. Instead it goes and gets the data out of the graphical widget that's displaying it. If the value is a number, it converts the displayed string representation of the number back to a number, otherwise it passes it back as a string.
So not only does the central controlling process not have control of the data, it's outsourced that responsibility to the GUI, and that in turn is using the display widget as its data store.
Whoever came up with this bright idea is a complete, raving, ... otter.
Imagine, in a distributed system that does in fact utilize a database for data storage you can lose all your active data if the GUI crashes.
(Oh, the problem turned out to be a data alignment mismatch due to the change in word sizes between the different platforms.)