Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[HttpClient] Improve the wording about asynchronous requests#21650

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
javiereguiluz wants to merge1 commit intosymfony:6.4
base:6.4
Choose a base branch
Loading
fromjaviereguiluz:tweak_httpclient

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

Choose a reason for hiding this comment

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

Suggested change
the HTTP requeststarts immediately, but the method returns without waiting for
the HTTP requestmight start immediately, but the method returns without waiting for

Copy link
MemberAuthor

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.

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

Choose a reason for hiding this comment

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

Suggested change
// the requeststarts, but execution continues without waiting
// the requestmight start, but execution continues without waiting

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

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

6.4

Development

Successfully merging this pull request may close these issues.

3 participants

@javiereguiluz@nicolas-grekas@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp