Skip to content

Releases: rsocket/rsocket-java

0.5.0

0.5.0 Pre-release
Pre-release

Choose a tag to compare

@benjchristensen benjchristensen released this 09 Jan 21:49
Start releasing

Trying to get releases working (and keep snapshots working)

v0.2.2: Merge pull request #154 from ReactiveSocket/requesthandler-interface

Choose a tag to compare

@robertroeser robertroeser released this 26 Jul 20:15
Make RequestHandler an interface

0.2.1

Choose a tag to compare

@NiteshKant NiteshKant released this 23 Jun 05:48
Disable Backup-Request / Retries. (#102)

* Disable Backup-Request / Retries.

**Problem**
There are bugs related to Backup-Request/Retries subscription.
The remaining part of the code is ok.

**Solution**
Disable the code in the ClientBuilder.

* Address comments

v0.2.0: Refactor ReactiveSocketServerHandler to be not shareable. (#94)

Choose a tag to compare

@rdegnan rdegnan released this 16 Jun 22:36
** Problem **
There's a memory leak in `ReactiveSocketServerHandler`, it keep adding entries
in the `duplexConnections` map but never remove them.

** Solution **
Instead of having only one `ReactiveSocketServerHandler`, and manage resources
manually, we let Netty allocate one instance per Channel. Then no resource
management is necessary.

** Modifications **
I refactored all the uage of `ReactiveSocketServerHandler` whithout changing
the logic. I also got rid of the method
```
public void channelReadComplete(ChannelHandlerContext ctx) {
    ctx.flush();
}
```
since we only use `writeAndFlush` in the DuplexConnection (we're sure there's
nothing to flush).

0.1.3

Choose a tag to compare

@NiteshKant NiteshKant released this 08 Jun 18:23
v0.1.3

Add missing file Help Unsafe object

0.1.2

Choose a tag to compare

@NiteshKant NiteshKant released this 03 Jun 23:23
Frame instance was referenced longer than required. (#88)

Problem:

`handleXXX` methods in `Responder` were closing over the passed `requestFrame` and using it later in the lifecycle of request processing.
 `Frame` objects and the underlying buffers are not designed to be retained after the scope of the parent method as these objects are threadlocal and reused. This causes issues when the frame object is referenced later in the request processing (eg: `cleanup()`)

 Solution:

 The only reason frame object was retained was to get the stream Id. This change pre-fetches the `streamId` and uses that from within the processing closure.

 Result:

 No more issue with frame access.

v0.1.1: Merge pull request #84 from ReactiveSocket/error-handling

Choose a tag to compare

@rdegnan rdegnan released this 26 May 23:48
Added error handling in Responder

v0.1.0: Merge pull request #83 from robertroeser/master

Choose a tag to compare

@robertroeser robertroeser released this 11 May 17:42
added toString for tracing

0.0.9

Choose a tag to compare

@stevegury stevegury released this 05 May 23:09

#82 adding a callback when a reactive socket is closed

v0.0.8

Choose a tag to compare

@robertroeser robertroeser released this 02 May 23:10
adding an exception classed TransportException which is thrown when t…