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

Diff between protocol specific properties and protocol properties #1101

Closed
zaheduzzaman opened this issue Jan 20, 2023 · 2 comments · Fixed by #1104
Closed

Diff between protocol specific properties and protocol properties #1101

zaheduzzaman opened this issue Jan 20, 2023 · 2 comments · Fixed by #1104

Comments

@zaheduzzaman
Copy link
Member

Protocol Specific Properties are defined in a transport- and
implementation-specific way to
permit more specialized protocol features to be used.
Too much reliance by an application on Protocol Specific Properties can significantly reduce the flexibility
of a transport services implementation to make appropriate
selection and configuration choices. Therefore, it is RECOMMENDED that
Protocol Properties are used for properties common across different protocols and that
Protocol Specific Properties are only used where specific protocols or properties are necessary.

Are Protocol Specific Properties and Protocol Properties same or different?

Also note that we are first time defining the Protocol Properties in the interface document ( described along with Connection Properties) and not introduced in the architecture document. I think we should be clear about what we are defining where and describing where. I would suggest use of cross reference rather describing everything again and again, which might create confusion and inconsistency.

@mwelzl
Copy link
Contributor

mwelzl commented Jan 20, 2023

Oh, this seems like a mistake (great catch, thanks!) - "Protocol Properties" don't exist, I think we only have "protocol-specific Properties".

@zaheduzzaman
Copy link
Member Author

I caught this when reading the implementation doc. So it should be fixed there as well.

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

Successfully merging a pull request may close this issue.

2 participants