3 ms·

"Completely broken" yet "we added a workaround [...] – so Safari users should be good to go" That seems rather contradictory

• magicalhippo 5y ago
  Why? At work we've had several cases where one API (or similar) turned out to be completely broken, yet we successfully implemented a workaround using another API. That doesn't change the fact that the API we initially tried to use was completely broken. Like, maybe the service we needed to supply with data had a REST API which turned out to be completely broken, so we ended up reverting to generating XML files and uploading that via SFTP. That the data ended up where it needed to doesn't change the fact that their REST API was broken.
  • Tepix 5y ago
    In this case it seems like a retry will change this API from "completely broken" to "working again".
    • magicalhippo 5y ago
      How so? I didn't mean broken as in the web server didn't respond or service wasn't running. I meant the API was broken, as in did not do the right thing.
      • Tepix 5y ago
        To ke "completely broken" means "broken beyond repair"
        • magicalhippo 5y ago
          That's not a definition I would agree with. Completely broken to me, in the context of API's at least, means it doesn't do at all what it is supposed, or documented, to do. A file server which claims to store files for late retrieval but saves all incoming files to /dev/null is completely broken from the user POV, while it's likely not beyond repair.