Skip to content

Don't send echo=true connection param#469

Open
lawrence-forooghian wants to merge 1 commit into
mainfrom
465-clarify-echoMessages-default
Open

Don't send echo=true connection param#469
lawrence-forooghian wants to merge 1 commit into
mainfrom
465-clarify-echoMessages-default

Conversation

@lawrence-forooghian
Copy link
Copy Markdown
Collaborator

The server's default behaviour is equivalent to echo=true.

Resolves #465.

The server's default behaviour is equivalent to `echo=true`.

Resolves #465.
Copy link
Copy Markdown
Member

@SimonWoolf SimonWoolf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure I see the need to deprecate RTN2b in favour of a new RTN2h given this is just restoring RTN2b to what it said originally, but shrug

@lawrence-forooghian
Copy link
Copy Markdown
Collaborator Author

not sure I see the need to deprecate RTN2b in favour of a new RTN2h given this is just restoring RTN2b to what it said originally, but shrug

"originally" when? because as mentioned in #198 (comment), the pre-that-PR-version of that spec point also suggested you were meant to always send the param

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

RTC1a needlessly requires sending the echo param with a default value

2 participants