Releases: ReactiveX/RxNetty
Releases · ReactiveX/RxNetty
0.3.15
- Issue 208 HTTPClient should discard a connection when response isn't completely consumed.
- Issue 229 Remove deprecated method
DefaultChannelWriter.getChannelHandlerContext()
. - Issue 237 Empty Client Request Buffers Are Not Released.
- Issue 243 HttpServerListener requestReadTimes metric value is incorrect.
- Issue 245 Race condition between write and flush in
HttpClient.submit()
. - Issue 248 Connection close cancels pending writes.
- Issue 249
BytesInspector
does not record events forByteBufHolder
andFileRegion
. - Issue 250 Fix connection closing and content stream behavior.
- Issue 251 Metric events for Request content source error and request write failure.
- Issue 252 Upgrade RxJava to 1.0.0-RC7.
Deprecation removals
- Issue 229 Remove deprecated method
DefaultChannelWriter.getChannelHandlerContext()
.
Artifacts: Maven Central
0.3.14
0.3.13
- Issue 214 HttpServerRequest should provide a way to access Netty channel.
- Issue 216 Remove deprecated HttpClientResponse and HttpServerRequest constructors.
- Issue 218 Migrate Branch Master -> 0.x.
- Issue 223 Client connections receiving SSE responses should never be pooled & reused.
- Issue 225 Unsubscribing from HttpClient.submit() should not close connection.
- Issue 226 Response should be flushed on
RequestHandler
's failure. - Issue 228
DefaultChannelWriter
should returnChannel
instead ofChannelHandlerContext
. - Issue 230 FlatResponseOperator does not emit any item if there is no content.
Deprecations
- Issue 228
DefaultChannelWriter.getChannelHandlerContext()
is deprecated.
Deprecation removals
- Issue 216 Remove deprecated HttpClientResponse and HttpServerRequest constructors.
Artifacts: Maven Central
0.3.12
- Issue 118 Javadoc errors when compiling with Java 8.
- Pull 196 Websocket client and server implementation.
- Pull 204 Add a generic Handler interface
- Issue 206 HttpClientResponse.getContent() will loose data if not eagerly subscribed.
- Issue 199 Invalid metric event used in DefaultChannelWriter.
Change in behavior
As part of Issue 206 the following change in behavior is done in this release:
Old Behavior
- Before this fix, the the
Observable
returned fromHttpClient.submit()
used to complete after the content of the response completed. - The content could be lost (this issue) if the content was subscribed out of the
onNext
call ofHttpClientResponse
New Behavior
- After this fix, the
Observable
returned fromHttpClient.submit()
completes immediately after one callback ofHttpClientResponse
. - The content can be subscribed out of the
onNext
call ofHttpClientResponse
till the content timeout as described in #206.
Artifacts: Maven Central
rxnetty-0.3.11
- Issue 195 RxClientImpl.shutdown() should not shutdown the eventloop.
Artifacts: Maven Central
rxnetty-0.3.10
- Issue 183 IdleConnectionsTimeoutMillis was not used by PooledConnectionFactory.
- Pull 186 Added a perf optimized helloworld example.
- Issue 187 Simplifying Aggregated Client Response usage.
- Pull 188 Adding an option to use a threadpool for Request/Connection processing.
Artifacts: Maven Central
rxnetty-0.3.9
- Pull 179 Monitors were not getting registered with servo.
- Pull 180 HTTP client/server metrics are not getting published to servo.
Artifacts: Maven Central
rxnetty-0.3.8
- Issue 150 Removed deprecated PoolStats.
- Issue 169 Removed ContentSource in favor of Observable for HttpClientRequest
- Issue 172 Missing connection pool events from client built by RxContexts constructs
- Issue 175 Optionally disable System time calls for metrics
- Issue 177 For HTTP server use channelReadComplete() to flush writes
Artifacts: Maven Central
rxnetty-0.3.7
- Issue 98 Added pluggable metrics infrastructure with rx-netty-servo implementation.
- Issue 106 Added TLS support for TCP & HTTP (HTTPS)
- Issue 115 ByteBuf leak fixed for both HTTP client and server.
- Issue 141 ServerSentEventEncoder modified to match the specifications and the decoder.
- Issue 158 HttpClientResponse and HttpServerRequest modified to take Subject instead of PublishSubject in the constructors.
- Issue 160 ServerRequestResponseConverter was using the same content subject for all requests on a channel.
- Issue 164 Removed flatmap() usage from HttpConnectionHandler for performance reasons.
- Issue 166 RxServer modified to optionally use a separate acceptor eventloop group.
- Issue 167 Not sending "Connection: keep-alive" header for HTTP 1.1 requests.
Artifacts: Maven Central
rxnetty-0.3.6
- Issue 111 Unsubscribing an SSE stream does not close the underlying connection
- Issue 126 HttpServer not compliant to HTTP 1.0 requests
- Issue 127 Revamp the examples.
- Issue 129 HTTP Redirect fails when there is a connection pool
- Issue 130 HTTP keep-alive connections not reusable with chunked transfer encoding
- Issue 131 HTTP redirect loop & max redirect detection is broken
- Issue 134 Provide default http header name for request ID in request context
- Pull 135 Added convenience method to add a single object with ContentTransformer to the HttpClientRequest
- Issue 139 HttpServerResponse.close() should be idempotent
- Issue 143 Write FullHttpResponse when possible
- Issue 145 ObservableConnection.cleanupConnection() does a blocking call.
Artifacts: Maven Central