Skip to content

Conversation

mostroverkhov
Copy link
Member

@mostroverkhov mostroverkhov commented May 14, 2018

Client and Server keep-alive implemented according to spec

Introduce RSocket server contract interceptor; move Setup frame validation from RSocketFactory

Move fragmentation from RSocketFactory to Connection interceptor

RSocketFactory API simplification

Renames: RSocketClient -> RSocketRequester, RSocketServer -> RSocketResponder, PluginRegistry -> InterceptorRegistry

Leak fix: release setup frame after decoding

Reimplemented fragmentation and reassembly logic as previously
It did not distinguish between Payload and Request* frames and crashed
consistently.

Introduce RSocket server contract interceptor; move Setup frame validation from RSocketFactory

Move fragmentation from RSocketFactory to Connection interceptor

RSocketFactory api simplification

renames: RSocketClient -> RSocketRequester, RSocketServer -> RSocketResponder, PluginRegistry -> InterceptorRegistry

rename RSocketInterceptor responder -> handler

Release setup frame after decoding
@mostroverkhov
Copy link
Member Author

@robertroeser

Reimplemented fragmentation and reassembly logic as previously
It did not distinguish between Payload and Request* frames and crashed
consistently. Also made sure FrameFragmenter does not leak frame contents
if unsubscribed before all fragments of frame are passed to subscriber
@mostroverkhov mostroverkhov changed the title Client & Server keep-alive improvements, RSocketFactory simplification Reworked fragmentation, Client & Server keep-alive improvements, RSocketFactory simplification May 16, 2018
@robertroeser robertroeser merged commit 185e469 into rsocket:master May 16, 2018
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.

2 participants