requests on same route working like a queue

[malletgaetan]

¿ problem ?

Hello everyone!

Just observed that multiple request for the same path were always finished in the same order than they came in.

For example:

REQUESTS["/" and "/"] -> 2s delay -> RESPONSE_1 -> 2s delay -> RESPONSE_2
--------
REQUESTS["/" and "test"] -> 2s delay -> RESPONSE _1 and RESPONSE_2

question

If a client make a request that take a LOT of time to finish, how to prevent other clients requesting the same route from being blocked?

code

import express from 'express'
const app = express()

app.get('/', function(req, res){
    setTimeout(() => res.send("Hello world!"), 2000)
})

app.get('/test', function(req, res){
     setTimeout(() => res.send("Hello world!"), 2000)
})

app.listen(3000)

Thanks! ✌(-‿-)✌

[micalevisk]

by not blocking the event loop, I guess?

[malletgaetan]

In the case 2 requests go at 9am00min00s on "/" route, one would respond 2s after and the other one 2s after to one response at 9am00min02s and the other at 9am00min04s, and that's the problem that i am facing, in the case my db request would take a lot of time, it would block other clients requeting the same route. Maybe i didn't understand what you're trying to say to me?

[micalevisk]

let's recap

what's the output of time ( curl "localhost:3000" & curl "localhost:3000/test" ) using the code you provided?

[malletgaetan]

the different route "test" is for the example that is actually working the good way, my question is if both requests are on the same path.
To respond to your question, the output is:

Hello world!Hello world!( curl "localhost:3000" & curl "localhost:3000/test"; )  0,01s user 0,00s system 0% cpu 2,015 total

[micalevisk]

right. You could try curl "localhost:3000" & curl "localhost:3000", and you'll see the same behavior.

[malletgaetan]

right. You could try curl "localhost:3000" & curl "localhost:3000", and you'll see the same behavior.

Your right! Its actually working the expected way using curl but not in the browser, i guess browser is waiting for first response to request on the same exact URL. Thanks for the help!