Skip to content

Upgrade websocket connection after completed response#586

Merged
normanmaurer merged 1 commit intonetty:masterfrom
sprsquish:fix-websocket-teardown
Sep 9, 2012
Merged

Upgrade websocket connection after completed response#586
normanmaurer merged 1 commit intonetty:masterfrom
sprsquish:fix-websocket-teardown

Conversation

@sprsquish
Copy link
Copy Markdown
Contributor

Channel handlers above the HttpEncoder may delay the repsonse being
written to the socket. We need to wait for the response to complete
before upgrading the pipeline.

Channel handlers above the HttpEncoder may delay the repsonse being
written to the socket. We need to wait for the response to complete
before upgrading the pipeline.
@veebs
Copy link
Copy Markdown
Member

veebs commented Sep 9, 2012

Should we apply to v3 as well?

@sprsquish
Copy link
Copy Markdown
Contributor Author

I think so, yes. Should I open a second pull request after this one is accepted?

@veebs
Copy link
Copy Markdown
Member

veebs commented Sep 9, 2012

Yes please. Just wait for @normanmaurer or @trustin to check it. It looks good to me.

@ghost ghost assigned normanmaurer Sep 9, 2012
normanmaurer added a commit that referenced this pull request Sep 9, 2012
Upgrade websocket connection after completed response
@normanmaurer normanmaurer merged commit fb17af4 into netty:master Sep 9, 2012
@normanmaurer
Copy link
Copy Markdown
Member

@sprsquish thanks for this! Would be perfect if you could also issue a pull-request for v3.

normanmaurer added a commit that referenced this pull request Sep 9, 2012
@normanmaurer
Copy link
Copy Markdown
Member

@sprsquish I made one modification to move all of the parts of the upgrade to the listener. Please review:

c6436ad

@sprsquish
Copy link
Copy Markdown
Contributor Author

Thanks!

Here's the backport to v3: #589

While working on that one, I realized I hadn't applied the fix to the client handshaker. Here's a pull request for that: #590

chrisvest pushed a commit to chrisvest/netty that referenced this pull request Apr 2, 2025
…s it is not needed anymore (netty#586)

Motivation:
Recently GraalVM added support for Apple M1.

Modifications:
- Remove the comment from resource-config.json file
- Update the version for native-maven-plugin

Result:
The comment in resource-config.json is not needed anymore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants