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.

Sign up for GitHub

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

Jump to bottom

Best practice for server response timing and asynchronous responses. #363

Open
dblodgett-usgs opened this issue Apr 28, 2022 · 1 comment
Open

Best practice for server response timing and asynchronous responses. #363

dblodgett-usgs opened this issue Apr 28, 2022 · 1 comment
Labels
best practice issues to be added to the best practice Cross-SWG Discussion

Comments

@dblodgett-usgs
Copy link
Contributor

We should draft a best practice for server response time and implementation of asynchronous behavior.

Once drafted, this should be raised as a cross SWG issue.

Any synchronous request should be held open for no more than X seconds (10?) any request longer than that should return a 300 series response with a redirect to a running process.
@chris-little chris-little changed the title Best practice for server response timing and asyncrounous responses. Best practice for server response timing and asynchronous responses. May 5, 2022
@chris-little chris-little added the best practice issues to be added to the best practice label May 12, 2022
@chris-little
Copy link
Contributor

This is linked to Issue #375. Could be explored in 2023 OGC/OSGeo/ASF sprint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
best practice issues to be added to the best practice Cross-SWG Discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dblodgett-usgs @chris-little