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

Create Remote Entity Connection Abstraction #112

Open
wmiaw opened this issue Jun 16, 2016 · 0 comments
Open

Create Remote Entity Connection Abstraction #112

wmiaw opened this issue Jun 16, 2016 · 0 comments
Assignees

Comments

@wmiaw
Copy link
Contributor

wmiaw commented Jun 16, 2016

MslControl currently accepts InputStream, OutputStream, or the MSL Url types for communication with the remote entity. Maybe this should be abstracted through some sort of remote entity connection interface, because it may be necessary to "close" and "open" connections for each MSL message or request/response pair.

This may be problematic for 3-message transactions, and due to expectation that a MslChannel is established and can be used for full-duplex communication. It may be that introducing this abstraction would be a bad idea because it breaks the expectation that an underlying protocol should be full-duplex and that overlay protocols like MSL should be agnostic. HTTP is the odd one out in that respect.

@wmiaw wmiaw self-assigned this Jun 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant