Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design and introduce retry strategy #25

Open
yanghua opened this issue Aug 20, 2024 · 0 comments
Open

Design and introduce retry strategy #25

yanghua opened this issue Aug 20, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@yanghua
Copy link
Collaborator

yanghua commented Aug 20, 2024

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.

@yanghua yanghua added the enhancement New feature or request label Aug 20, 2024
@yanghua yanghua self-assigned this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant