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

Complete the websocket ramp set #66

Closed
Licenser opened this issue Feb 25, 2020 · 3 comments
Closed

Complete the websocket ramp set #66

Licenser opened this issue Feb 25, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request offramp Offramps onramp Onramps

Comments

@Licenser
Copy link
Member

Describe the problem you are trying to solve

At the moment we only have half the WebSocket ramps.

we have a WebSocket server as an onramp and a WebSocket client as an offramp. To complete the set we should add a WebSocket client onramp and a WebSocket server offramp.

Describe the solution you'd like

The WebSocket client onramp would connect to a given WebSocket server and publish all messages from that server into the connected pipelines.

The WebSocket server offramp would allow clients to connect and send the events it receives to all clients that are connected at the time of arrival.

@Licenser Licenser added enhancement New feature or request onramp Onramps offramp Offramps labels Feb 25, 2020
@Licenser
Copy link
Member Author

This goes hand in hand with linked transports ( #64 ) :) tossing it to @anupdhml

@mfelsche
Copy link
Member

FTR this should be solved when we implement Connectors: tremor-rs/tremor-rfcs#32

@Licenser
Copy link
Member Author

This is done with connectors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request offramp Offramps onramp Onramps
Projects
None yet
Development

No branches or pull requests

3 participants