Skip to content

Conversation

@robertroeser
Copy link
Member

No description provided.

robertroeser added a commit that referenced this pull request Aug 17, 2015
switch request/response to send NEXT_COMPLETE instead of a NEXT, and a COMPLETE frame
@robertroeser robertroeser merged commit 4d35051 into rsocket:master Aug 17, 2015
stevegury pushed a commit that referenced this pull request Jun 8, 2016
stevegury added a commit that referenced this pull request Jun 8, 2016
* Refactor Factory to Connector + Implement availability

Problem
We need to comply with the recent refactoring "Factory to Connector" introduced
in reactivesocket-java. Also, implementation of DuplexConnection have to return
an availability.

Solution
The Factory to Connector refactoring is pretty straight forward.

All implementations of DuplexConnection return an availability which directly
map the state of the underlying resource (0.0 if the resource is closed, 1.0
otherwise). This will greatly help the load-balancer to select a valid
connection.

I removed the blocking method from reactivesocket-java, so I moved some utility
blocking code inside the TestUtil class.

Clean-up of the Netty implementation, remove unused args, explicitey specify
tcp socket configuration.

Shortened the toString name to ease log-reading.

Bug
All DuplexConnection implementations now cancel the subscription when an exception
occurs. This fix the problem, where the Keep-Alive Observable kept trying to
send a keep-alive on a closed connection.

* Refactor the TestUtil helper to return CompletableFuture

* rs version

* Restore rs dependency to latest.release

* Remove mavenLocal in gradle build file

* Propagate cancellation in all cases

* Use helper method from ReactiveSocket Unsafe
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