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.

Sign up for GitHub

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

Jump to bottom

Octets that are sent twice #1353

Merged
merged 4 commits into from May 15, 2018
Merged

Octets that are sent twice #1353

merged 4 commits into from May 15, 2018

Commits on May 14, 2018

  1. Octets that are sent twice 

    This is obvious, but never stated.  We discussed checking that they stay constant and agreed that requiring a check would be crazy.  However, we never wrote anything down.  I think that a MAY is fine.
    @martinthomson
    martinthomson committed May 14, 2018
    Copy the full SHA
    85a8ab1 View commit details
    Browse the repository at this point in the history

Commits on May 15, 2018

  1. Insist on being able to deliver in order 

    But don't imply an absolute requirement to do so.

It seems like an opportune moment to point out that no provision is made for partial reliability either.
    @martinthomson
    martinthomson committed May 15, 2018
    Copy the full SHA
    4cdf040 View commit details
    Browse the repository at this point in the history

  2. ordered stream

    @martinthomson
    martinthomson committed May 15, 2018
    Copy the full SHA
    490c00a View commit details
    Browse the repository at this point in the history

  3. Able to

    @martinthomson
    martinthomson committed May 15, 2018
    Copy the full SHA
    7b4cbf1 View commit details
    Browse the repository at this point in the history