Skip to content

Upgrade connection after completed response#589

Merged
normanmaurer merged 1 commit intonetty:3from
sprsquish:upgrading-websocket-connections
Sep 9, 2012
Merged

Upgrade connection after completed response#589
normanmaurer merged 1 commit intonetty:3from
sprsquish:upgrading-websocket-connections

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.
@ghost ghost assigned normanmaurer Sep 9, 2012
normanmaurer added a commit that referenced this pull request Sep 9, 2012
Upgrade connection after completed response
@normanmaurer normanmaurer merged commit 8f4f6a1 into netty:3 Sep 9, 2012
@normanmaurer
Copy link
Copy Markdown
Member

Thanks again !

@veebs
Copy link
Copy Markdown
Member

veebs commented Sep 10, 2012

Thanks. I've also run the changes against the AutoBahn test cases and everything passes.

No big changes in performance.

Netty 3.5.7 without the changes
Netty with changes

@normanmaurer normanmaurer mentioned this pull request Apr 1, 2013
chrisvest pushed a commit to chrisvest/netty that referenced this pull request Apr 2, 2025
Motivation:

We should run our testsuite with '-Xcheck:jni' to ensure we catch bugs
in our JNI code which could later cause issues like crashes

Modifications:

- Add -Xcheck:jni
- Add -ea

Result:

Testsuite will be able to catch more JNI bugs
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