Skip to content

Conversation

@javiereguiluz
Copy link
Member

A minor change to be more precise about the actual behavior of the HTTP client.

Responses are always asynchronous, so that the call to the method returns
immediately instead of waiting to receive the response::
Symfony's HTTP client is asynchronous by default. When you call ``request()``,
the HTTP request starts immediately, but the method returns without waiting for
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
the HTTP request starts immediately, but the method returns without waiting for
the HTTP request might start immediately, but the method returns without waiting for

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But if we say "might start" ... then we need to explain when it starts and when it doesn't. Please, share some details about this. Thanks.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know, curl does. We don't care here, that's the whole point

a response. Your code only blocks when you actually need the response data::

// code execution continues immediately; it doesn't wait to receive the response
// the request starts, but execution continues without waiting
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// the request starts, but execution continues without waiting
// the request might start, but execution continues without waiting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants