nextcloud / nextcloud/Android-SingleSignOn
Allow setting connect/read/write timeouts for requests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 74
- Forks
- 36
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 17
Description
Right now there is no option to control the default timeouts (connect / read / write) for requests that are defined by the Nextcloud Files App. E.g. the Nextcloud News App makes a long running request for adding new feeds. The duration is basically determined by how fast the server is because the request will wait until the feed has been added successfully on the server side.
Therefore allowing single requests to have a longer / different timeout would be ideal.
I found an interesting article where someone explains a way to set timeouts dynamically via Headers that will be interpreted by OkHTTP later on. I believe this setup would fit perfectly fine into the SSO Lib: https://www.jndiary.com/post/setup-timeout-dynamically-with-retrofit
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked article about dynamic OkHTTP timeouts, then inspect the SSO Lib request path to find where Nextcloud Files App requests are configured. Determine how per-request connect, read, and write timeout values should be supplied, and verify that a long-running request can use different defaults without changing other requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100