You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
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 text was updated successfully, but these errors were encountered: