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

Request a connector to [capture from | materialize to] [your favorite system] #1816

Open
worldturtlefarm opened this issue Aug 15, 2024 · 1 comment
Labels
new connector Request a new connector to an external system

Comments

@worldturtlefarm
Copy link

System Name

Websocket Connector

Type

Capture

Details

Hi there! My name is Jacob Leonard, I've made a few suggestions in the past while working at previous companies, but I wanted to make a request for a general gap in the market service offerings that Im seeing for websockets. Is there any plan on the roadmap for estuary to add a more general websocket connector? or could I do something like that with the CLI?

@worldturtlefarm worldturtlefarm added the new connector Request a new connector to an external system label Aug 15, 2024
@psFried
Copy link
Member

psFried commented Aug 20, 2024

@worldturtlefarm would you be wanting to capture data that clients send via websocket? If so, then is there a specific protocol that you'd want to see supported? Websockets are move like a transport than a full-fledged protocol. There would need to be some sort of protocol that's able to represent desired transaction boundaries and commit results, etc. We could invent one, but that seems at odds with the idea of a "general websocket" connector.

Do you happen to have a specific use-case in mind that you could share?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new connector Request a new connector to an external system
Projects
None yet
Development

No branches or pull requests

2 participants