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

hi,about the http sequence #417

Open
suppersam1 opened this issue Apr 12, 2023 · 3 comments
Open

hi,about the http sequence #417

suppersam1 opened this issue Apr 12, 2023 · 3 comments

Comments

@suppersam1
Copy link

Hi, may I ask if the HTTP requests from the same route in the crow are strictly executed in sequence, and if the requests from the same route are stored in a queue and then executed in FIFO order

@suppersam1
Copy link
Author

I'm not very familiar with boost:: asio:: io_ service, I have looked at the code for crow and found that without opening multiple threads, only one thread calls boost:: asio:: io_service. run() method. Does this mean that HTTP requests will be executed sequentially?

@gittiver
Copy link

gittiver commented Apr 19, 2023

not exactly, io processes have also wait states where the next request can be started. so they can be executed at least partially overlapping.
maybe that is a good start to read: https://think-async.com/Asio/asio-1.26.0/doc/asio/overview/model/async_ops.html

@suppersam1
Copy link
Author

not exactly, io processes have also wait states where the next request can be started. so they can be executed at least partially overlapping. maybe that is a good start to read: https://think-async.com/Asio/asio-1.26.0/doc/asio/overview/model/async_ops.html

Is there any way to solve this problem?The Crow framework seems unable to strictly follow the order of HTTP requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants