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

Review TransportServer interface #1

Open
flowersinthesand opened this issue Mar 20, 2015 · 0 comments
Open

Review TransportServer interface #1

flowersinthesand opened this issue Mar 20, 2015 · 0 comments

Comments

@flowersinthesand
Copy link
Member

TransportServer consumes resource and produces ServerTransport. For example, HttpTransportServer consumes ServerHttpExchange and produces streaming transport and long polling transport. But, that's all. It is the only purpose of TransportServer.

  • Interface name
    Server also consumes transport and produces socket but besides other functionalities like finding socket are also provided as Cettia server. On the other hand, TransportServer does not and should not provide such unnecessary features. In that sense, I feel TransportServer is awkward but couldn't find other proper name. Otherwise, we may need a general term for such interface.
  • Maven artifact
    For those who want to use Cettia transport only e.g. to build custom protocol on top of Cettia transport layer, cettia-transport-server module should be separated from cettia-server module.
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

No branches or pull requests

1 participant