Status quo

Symfony currently implicitly starts the session when user management is used. This is necessary because the user is fetched from the session.

Those lines will implicitly start the session.

Feature request

Symfony currently does not close the session after it's accessed. This means that the request will acquire a lock on the session file and make other requests wait for the entire request to finish, even if the session is not used after Symfony authenticates the user.

This could be solved rather easily by adding a $session->save(); call after accessing the values from the session. This will release the lock and allow other requests to access the session file.

This could have a few potential issues:

1. More overhead because of additional serialization and deserialization of session data
2. Race conditions where requests must be executed in a certain order, start to finish

The big pro would be allowing parallel requests.

WDYT?