- [Issue 277] (https://github.com/ReactiveX/RxNetty/issue/277) StackOverflow while draining
UnicastContentSubject
- [Issue 287] (https://github.com/ReactiveX/RxNetty/issue/287) Flush HTTP response on completion of
RequestHandler.handle()
- [Issue 288] (https://github.com/ReactiveX/RxNetty/issue/288) Upgrade to rx-java 1.0.1
Artifacts: Maven Central
- [Pull 275] (#275) Changing package and artifact org from netflix.rxjava -> io.reactivex.
Artifacts: Maven Central
- [Issue 257] (#257) Support relative URIs for redirect.
- [Issue 269] (#269)
ServerSentEventDecoder
stops decoding after receiving an illegal field. - [Issue 270] (#270) HttpClient should only do relative redirects.
- [Issue 271] (#271) URI fragment must be inherited by the redirect location.
- [Issue 272] (#272) Guaranteeing sequential notifications from operators/Subjects.
- [Issue 270] (#270) HttpClient should only do relative redirects.
Artifacts: Maven Central
- [Issue 267] (#267) Change ServerSentEvent to store data as
ByteBuf
. - [Pull 265] (#265) Release
LastHttpContent
when it is not readable. - [Issue 263] (#263) Rename eventloops.
- [Issue 209] (#209) Deprecate all SSE classes in io.reactivex.netty.protocol.text.sse.
- [Issue 205] (#205) Move SSE related class to the http package.
- [Issue 220] (#220) Confusing ServerSentEvent API causes emitting empty "event" fields.
- [Issue 222] (#222) SSE API is error prone, and lacks flexibility for common usage patterns.
- [Issue 30] (#30) SSE codec re-implementation.
- [Issue 209] (#209) Deprecate all SSE classes in io.reactivex.netty.protocol.text.sse.
Artifacts: Maven Central
- [Issue 258] (#258) Include port in the HTTP HOST header.
- [Issue 259] (#259) Support native netty protocol as a runtime choice.
- [Issue 260] (#260) Convert
RxEventLoopProvider
andMetricEventsListenerFactory
to abstract classes. - [Issue 261] (#261)
ServerSentEventEncoder
is sub-optimal in using StringBuilder
- [Issue 260] (#260) Convert
RxEventLoopProvider
andMetricEventsListenerFactory
to abstract classes.
Artifacts: Maven Central
- [Issue 208] (#208) HTTPClient should discard a connection when response isn't completely consumed.
- [Issue 229] (#229) Remove deprecated method
DefaultChannelWriter.getChannelHandlerContext()
. - [Issue 237] (#237) Empty Client Request Buffers Are Not Released.
- [Issue 243] (#243) HttpServerListener requestReadTimes metric value is incorrect.
- [Issue 245] (#245) Race condition between write and flush in
HttpClient.submit()
. - [Issue 248] (#248) Connection close cancels pending writes.
- [Issue 249] (#249)
BytesInspector
does not record events forByteBufHolder
andFileRegion
. - [Issue 250] (#250) Fix connection closing and content stream behavior.
- [Issue 251] (#251) Metric events for Request content source error and request write failure.
- [Issue 252] (#252) Upgrade RxJava to 1.0.0-RC7.
- [Issue 229] (#229) Remove deprecated method
DefaultChannelWriter.getChannelHandlerContext()
.
Artifacts: Maven Central
- [Issue 233] (#233) Using DefaultFactories.TRUST_ALL causes SelfSignedSSLEngineFactory to Error on Certain Systems.
- [Pull 219] (#219) Http RequestHandler to serve files.
- [Issue 235] (#235) HttpServer with non-aggregated request is broken.
Artifacts: Maven Central
- [Issue 214] (#214) HttpServerRequest should provide a way to access Netty channel.
- [Issue 216] (#216) Remove deprecated HttpClientResponse and HttpServerRequest constructors.
- [Issue 218] (#218) Migrate Branch Master -> 0.x.
- [Issue 223] (#223) Client connections receiving SSE responses should never be pooled & reused.
- [Issue 225] (#225) Unsubscribing from HttpClient.submit() should not close connection.
- [Issue 226] (#226) Response should be flushed on
RequestHandler
's failure. - [Issue 228] (#228)
DefaultChannelWriter
should returnChannel
instead ofChannelHandlerContext
. - [Issue 230] (#230) FlatResponseOperator does not emit any item if there is no content.
- [Issue 228] (#228)
DefaultChannelWriter.getChannelHandlerContext()
is deprecated.
- [Issue 216] (#216) Remove deprecated HttpClientResponse and HttpServerRequest constructors.
Artifacts: Maven Central
- [Issue 118] (#118) Javadoc errors when compiling with Java 8.
- [Pull 196] (#196) Websocket client and server implementation.
- [Pull 204] (#204) Add a generic Handler interface
- [Issue 206] (#206) HttpClientResponse.getContent() will loose data if not eagerly subscribed.
- [Issue 199] (#199) Invalid metric event used in DefaultChannelWriter.
As part of [Issue 206] (#206) the following change in behavior is done in this release:
- 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
- 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
- [Issue 195] (#195) RxClientImpl.shutdown() should not shutdown the eventloop.
Artifacts: Maven Central
- [Issue 183] (#183) IdleConnectionsTimeoutMillis was not used by PooledConnectionFactory.
- [Pull 186] (#186) Added a perf optimized helloworld example.
- [Issue 187] (#187) Simplifying Aggregated Client Response usage.
- [Pull 188] (#188) Adding an option to use a threadpool for Request/Connection processing.
Artifacts: Maven Central
- [Pull 179] (#179) Monitors were not getting registered with servo.
- [Pull 180] (#180) HTTP client/server metrics are not getting published to servo.
Artifacts: Maven Central
- [Issue 150] (#150) Removed deprecated PoolStats.
- [Issue 169] (#169) Removed ContentSource in favor of Observable for HttpClientRequest
- [Issue 172] (#172) Missing connection pool events from client built by RxContexts constructs
- [Issue 175] (#175) Optionally disable System time calls for metrics
- [Issue 177] (#177) For HTTP server use channelReadComplete() to flush writes
Artifacts: Maven Central
- [Issue 98] (#98) Added pluggable metrics infrastructure with rxnetty-servo implementation.
- [Issue 106] (#106) Added TLS support for TCP & HTTP (HTTPS)
- [Issue 115] (#115) ByteBuf leak fixed for both HTTP client and server.
- [Issue 141] (#141) ServerSentEventEncoder modified to match the specifications and the decoder.
- [Issue 158] (#158) HttpClientResponse and HttpServerRequest modified to take Subject instead of PublishSubject in the constructors.
- [Issue 160] (#160) ServerRequestResponseConverter was using the same content subject for all requests on a channel.
- [Issue 164] (#164) Removed flatmap() usage from HttpConnectionHandler for performance reasons.
- [Issue 166] (#166) RxServer modified to optionally use a separate acceptor eventloop group.
- [Issue 167] (#167) Not sending "Connection: keep-alive" header for HTTP 1.1 requests.
Artifacts: Maven Central
- [Issue 111] (#111) Unsubscribing an SSE stream does not close the underlying connection
- [Issue 126] (#126) HttpServer not compliant to HTTP 1.0 requests
- [Issue 127] (#127) Revamp the examples.
- [Issue 129] (#129) HTTP Redirect fails when there is a connection pool
- [Issue 130] (#130) HTTP keep-alive connections not reusable with chunked transfer encoding
- [Issue 131] (#131) HTTP redirect loop & max redirect detection is broken
- [Issue 134] (#134) Provide default http header name for request ID in request context
- [Pull 135] (#135) Added convenience method to add a single object with ContentTransformer to the HttpClientRequest
- [Issue 139] (#139) HttpServerResponse.close() should be idempotent
- [Issue 143] (#143) Write FullHttpResponse when possible
- [Issue 145] (#145) ObservableConnection.cleanupConnection() does a blocking call.
Artifacts: Maven Central
- [Issue 55] (#55) Add wire debugging functionality
- [Issue 88] (#88) Move host and port to RxClient method signature
- [Issue 90] (#90) Server onError Handling
- [Issue 101] (#101) Infrastructure Contexts
- [Issue 105] (#105) AbstractClientBuilder.SHARED_IDLE_CLEANUP_SCHEDULER prevents application from closing.
- [Pull 108] (#108) UDP support.
- [Issue 113] (#113) Implement Redirect as an Rx Operator.
- [Issue 114] (#114) Remove numerus dependency from rxnetty-core.
- [Pull 116] (#116) Added toString() to ServerInfo for better inspection.
- [Issue 117] (#117) RxClientImpl mutates netty's bootstrap per connection
- [Issue 119] (#119) "Transfer-encoding: chunked" not set for HTTP POST request.
Artifacts: Maven Central
Skipped release due to manual tag creation.