Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #223 #225 #226 #214 #228 #230 #227

Merged
merged 5 commits into from
Sep 7, 2014
Merged

Conversation

NiteshKant
Copy link
Member

Issue #223 Force closing underlying physical connection whenever an SSE response is received on it.
Issue #225 Now the connection close is triggered after the content completes or the sole subscriber of the content unsubscribes.
Issue #226 Flushing response when RequestHandler emits an error or throws an unexpected error.
Issue #214 HttpServerRequest should provide access to the underlying Channel.
Issue #228 Provided getChannel() in DefaultChannelWriter instead of getChannelHandlerContext().
Issue #230 FlatResponseOperator does not emit any item if there is no content.

Nitesh Kant added 5 commits September 4, 2014 21:56
…d never be pooled & reused)

Channel attribute "rxnetty_http_discard_connection" is used by `ObservableConnection` to discard a connection on close. SSE Inbound handler sets this attribute as a connection on which SSE response has started should never be pooled.
 Issue 226: Flushing response when `RequestHandler` emits an error or throws an unexpected error.
 Issue 225: Connection close for HttpClient.submit() is now done when the content is completed or the (only) subscriber to the content subject unsubscribes.
If no one subscribes to the UnicastContentSubject, for HttpClientResponse, the connection would never be closed.

For this reason we should also call the onUnubscribe action when the content is disposed.
Issue ReactiveX#214 Provde getChannel() method in HttpServerRequest
Issue ReactiveX#228 Provide getChannel() method in DefaultChannelWriter and deprecate getChannelHandlerContext()
…here is no content.)

Also, fixed the test failure for previous PR
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.

1 participant