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

Define WebSocketSubscription2021 type for Solid Notifications #28

Merged
merged 7 commits into from Jan 20, 2022

Conversation

acoburn
Copy link
Member

@acoburn acoburn commented Dec 23, 2021

This defines the WebSocketSubscription2021 type in an independent specification document.

@acoburn acoburn changed the title Define WebSocketSubscription2021 type Define WebSocketSubscription2021 type for Solid Notifications Dec 23, 2021
Copy link
Member

@csarven csarven left a comment

Choose a reason for hiding this comment

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

I suppose it is feasible to have a WebSocket endpoint that accepts different subscription types. In that case, the protocol parameter should have a value. If the general idea / best practice for servers to allow only one type of subscription per endpoint, this should be mentioned. See the comments on some things to consider towards failing or opening a connection.

websocket-subscription-2021.html Outdated Show resolved Hide resolved
Co-authored-by: Sarven Capadisli <info@csarven.ca>
@acoburn
Copy link
Member Author

acoburn commented Jan 11, 2022

It is entirely possible for a WebSocket endpoint to support different subscription types. As for whether it's best to have one endpoint per type or to put all of the types on a single endpoint -- that's really an implementation decision

@acoburn acoburn merged commit a5968d2 into main Jan 20, 2022
@acoburn acoburn deleted the websocket-document branch January 20, 2022 15:27
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

Successfully merging this pull request may close these issues.

None yet

3 participants