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

Write down implicit assumptions made about default configurations and compatibility #26

Closed
chris-wood opened this issue Nov 14, 2017 · 3 comments
Assignees

Comments

@chris-wood
Copy link

  1. Must be possible to use Post Sockets on one side and BSD on the other side
  2. Carriers must use sane defaults and work without configurations or custom PSCs
  3. ...?
@britram
Copy link
Contributor

britram commented Nov 14, 2017

  1. must not require signaling beyond that provided by the PSI.
  2. "must be implementable" but I don't really think we need to write that down.

@csperkins
Copy link
Contributor

  1. transport selection magic must give a predictable outcome

@britram
Copy link
Contributor

britram commented Nov 14, 2017

4a. we might want to write down that "must be efficiently implementable in POSIX C without any additional library/kernel support" is a non-goal -- ready() requires asynchronicity, which you can fake without something like libevent, but not in a way that is at all nice.

@chris-wood chris-wood self-assigned this Nov 16, 2017
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

3 participants