𝗪𝗛𝗘𝗡 𝗦𝗢𝗙𝗧𝗪𝗔𝗥𝗘 𝗠𝗨𝗦𝗧 𝗛𝗔𝗡𝗗𝗟𝗘 𝗨𝗡𝗖𝗘𝗥𝗧𝗔𝗜𝗡𝗧𝗬
Not every request receives an immediate, unambiguous response.
A wallet may lose connectivity after submitting a transaction. An API may time out while the transaction continues processing. A user may refresh the page before the final status becomes available.
TRON applications should be designed to handle these situations without falsely reporting success or encouraging duplicate actions.
A robust workflow can preserve the transaction reference, check the available status information, and clearly explain what the user should do next.
The key is to distinguish uncertainty from failure.
Systems become more dependable when they are designed for imperfect conditions instead of assuming every operation follows the ideal path.
@trondao
@justinsuntron
#TRONEcoStar
Not every request receives an immediate, unambiguous response.
A wallet may lose connectivity after submitting a transaction. An API may time out while the transaction continues processing. A user may refresh the page before the final status becomes available.
TRON applications should be designed to handle these situations without falsely reporting success or encouraging duplicate actions.
A robust workflow can preserve the transaction reference, check the available status information, and clearly explain what the user should do next.
The key is to distinguish uncertainty from failure.
Systems become more dependable when they are designed for imperfect conditions instead of assuming every operation follows the ideal path.
@trondao
@justinsuntron
#TRONEcoStar