Ben Christensen

Here is an example I'm considering using for a presentation on Tuesday. It's buggy right now (as shown above) but demonstrates the goals of interop while going through non-trivial operators...

I don't understand your question. Can you elaborate please?

It should `onError` that single stream if flow control is not respected and `cancel` upwards. @tmontgomery Should this be defined in the spec for how this should be handled?

Should the required/suggested behavior be documented as per https://github.com/ReactiveSocket/reactivesocket/issues/133 ?

- [x] Separate single-threaded and thread-safe API layers Ondrej and I discussed a possible layout as follows... Thread-safe layer is: - RSocketServer, RSocketClient, RSocketRequester, RSocketResponder Single-threaded layer is: - RSocketStateMachine...

- [ ] Observers/Singles overrides of onComplete/onNext calling super to release?

- [ ] default maximum request(n) over network to something reasonable (128?)

- [x] simplify examples (subscribe overloads with lambdas for example) - [x] RSocket requestResponse unit tests - [x] RSocket requestStream unit tests - [x] RSocket requestChannel unit tests - [...

- [ ] consistent naming convention of methods in public APIs (either getter or not getter style) - [x] collapse ConnectionSetupRequest and SetupParameters - [x] collapse ConnectionResumeRequest and ResumeParameters -...

Which of these still need to be done? If any perhaps we should split them out into their own tasks now since the sprint is more-or-less complete to get the...