You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
Probably similar usecases as the websocket server.
But in general, any time for when its to allow clients to connect to vector instead of having to change vector for each new client. Or other similar usecases.
Attempted Solutions
We are currently running a standalone rust server after vector. that clients then connect to.
Proposal
Either add a mode: server to the current socket sink, or a new socket server sink.
We are happy to attempt an implementation if the feature would be approved.
References
No response
Version
vector 0.41.1
The text was updated successfully, but these errors were encountered:
A note for the community
Use Cases
Probably similar usecases as the websocket server.
But in general, any time for when its to allow clients to connect to vector instead of having to change vector for each new client. Or other similar usecases.
Attempted Solutions
We are currently running a standalone rust server after vector. that clients then connect to.
Proposal
Either add a mode: server to the current socket sink, or a new socket server sink.
We are happy to attempt an implementation if the feature would be approved.
References
No response
Version
vector 0.41.1
The text was updated successfully, but these errors were encountered: