Fastcgi msg_id always 1?

I was looking at the fastcgi, I found out that all fcgi request have a
msg_id of 1?

What happens when more than 1 fcgi requests comes in and first one is
still being handled. how does the fcgi server know the the difference
in requests? Usually each request has it own connection, but if
keepalive is on the then many request can come in on the same
connection.

I am use “ab” to test the nginx+ fastcgi server response time.

Hello!

On Thu, Sep 29, 2011 at 03:15:55PM +0800, Shaun savage wrote:

I was looking at the fastcgi, I found out that all fcgi request have a
msg_id of 1?

Yes.

What happens when more than 1 fcgi requests comes in and first one is
still being handled. how does the fcgi server know the the difference
in requests? Usually each request has it own connection, but if
keepalive is on the then many request can come in on the same connection.

The id is only need to be unique when multiple request exists in
parallel within a single connection. This is not the case even
with keepalive used.

Maxim D.

On Thu, Sep 29, 2011 at 3:35 PM, Maxim D. [email protected]
wrote:

still being handled. how does the fcgi server know the the difference
in requests? Usually each request has it own connection, but if
keepalive is on the then many request can come in on the same connection.

The id is only need to be unique when multiple request exists in
parallel within a single connection. This is not the case even
with keepalive used.

E.g multiplexing not supported.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs