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

Sockets to streams #210

Closed
wants to merge 7 commits into from
Closed

Sockets to streams #210

wants to merge 7 commits into from

Conversation

Threated
Copy link
Member

@Threated Threated commented Sep 9, 2024

This changes beams socket protocol from the bidirectional sockets interface to a unidirectional streaming interface. This change was motivated by several practical issues with proxies that did not allow http request upgrades by default.
The new approach uses streaming http bodies which should be supported by all regular proxies.

Open questions:

  • Should we rename the endpoints from /v1/sockets to /v1/stream[s]
  • There seems to be a regression with the tasks endpoint

@Threated Threated requested a review from TKussel September 9, 2024 08:51
This changes beams socket protocol from the bidirectional sockets
interface to a unidirectional streaming interface.
This change was motivated by serveral practical issues with proxies that
did not allow http request upgrades by default.
The new approach uses streaming http bodies which should be supported by
all regular proxies.
@Threated Threated force-pushed the feat/rework-sockets branch from 0882f57 to cec5122 Compare September 9, 2024 14:46
@TKussel
Copy link
Member

TKussel commented Oct 17, 2024

Reanaming the endpoint to v1/streams is a good suggestion. They are streams and unidirectional as well.

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.

2 participants