The current implementation of tosfs gives high priority to functional interfaces and does not invest much effort in robustness and stability. However, there is no doubt that these characteristics are necessary for a production-ready client. Therefore, this issue is created to track the design and functional implementation of robustness.
Overall, in terms of the design, it needs to understand the status codes returned by the TOS service and make some recovery logics based on the status codes, such as reading and writing positions, connection reestablishment, etc.
The current implementation of tosfs gives high priority to functional interfaces and does not invest much effort in robustness and stability. However, there is no doubt that these characteristics are necessary for a production-ready client. Therefore, this issue is created to track the design and functional implementation of robustness.
Overall, in terms of the design, it needs to understand the status codes returned by the TOS service and make some recovery logics based on the status codes, such as reading and writing positions, connection reestablishment, etc.