Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactoring #19

Merged
merged 9 commits into from
Jan 28, 2014
Merged

Refactoring #19

merged 9 commits into from
Jan 28, 2014

Conversation

NiteshKant
Copy link
Member

Following were the major design goals in this refactoring:

  1. Modify java packages to better indicate what they contain.
  2. Have a common client & server implementation that can be used by all connection oriented protocols.
  3. Simplify netty's pipeline to have a thin adapter to convert netty's messages to Rx Observables.
  4. Remove any custom callbacks which can be obtained by having a handler in the netty pipeline.
  5. Model all protocol handling as netty's pipeline handlers.

TODO:

  1. Fix groovy examples.
  2. Http request execution should be cancelled as much as possible when the subscription is unsubscribed.

Nitesh Kant added 9 commits January 18, 2014 12:43
…at we do not need.

Fixed a compilation error due to package name changes.
The major changes are these:

1) Have a single client & server implementation that can be used for all connection oriented transport & application protocols.
2) Renamed the Protocolhandler to NettyPipelineConfigurator as it does not do any protocol handing per se, it just configures the pipeline. ProtocolHandler was a misnomer.
3) The Client & Server has only 2 Rx specific handlers on top of the netty pipeline, one for connection lifecycle & another for converting netty's events to Rx Observer callbacks.

 The following are the TODOs as of now:

 1) Http implementation is not at all complete. Although the pipeline configurators are as we want them.
 2) Groovy examples needs to be fixed.
 3) Http unit tests are commented out as the client is going to change drastically.
TODO:

1) Fix HTTP unit tests.
2) Fix SSE server/client interaction. The server does not seem to be publishing the correct SSE data, the SSEDecoder does not publish events.
3) Fix groovy examples.
4) Add read timeout handler support.
5) HttpClient may create a request eagerly for pooled connections (which are not supported as of now)
1) The SSEInboundHandler was not passing any unknown messages through it.
2) The SSE encoder was putting a single new line instead of two to indicate end of message.
3) Introduced the read timeout functionality. TODO: Remove the timeout handler.
1) Extracted an interface for the client, which will help us implement pooled, non-pooled, pooled per route etc. type of clients.
2) Cleaned up the PipelineConfigurators to remove "handler" reference & also clarified the names to better suit the behavior. Added few more factory methods.
@g9yuayon
Copy link
Contributor

I'll just merge the pull request so I can start using the updated API in Mantis.

g9yuayon added a commit that referenced this pull request Jan 28, 2014
@g9yuayon g9yuayon merged commit e6fb4ae into ReactiveX:master Jan 28, 2014
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