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

[Server] Add support for Unix domain sockets (UDS) #25

Closed
clue opened this issue Sep 19, 2015 · 7 comments
Closed

[Server] Add support for Unix domain sockets (UDS) #25

clue opened this issue Sep 19, 2015 · 7 comments
Assignees
Milestone

Comments

@clue
Copy link
Member

clue commented Sep 19, 2015

No description provided.

@clue
Copy link
Member Author

clue commented Sep 19, 2015

See PR #17 for possible implementation.

@clue
Copy link
Member Author

clue commented Feb 13, 2017

Progress update: Feature branch is ready, I'll file a PR for this once the v0.5.0 release is out :shipit:

@WyriHaximus
Copy link
Member

🎉

@clue clue modified the milestones: v0.5.2, v0.5.1 Mar 9, 2017
@clue clue modified the milestones: v0.8.0, v0.5.2 Mar 28, 2017
@clue
Copy link
Member Author

clue commented Mar 28, 2017

Deferred to future release as per #75

@clue clue changed the title Add support for Unix domain sockets (UDS) [Server] Add support for Unix domain sockets (UDS) Apr 10, 2017
@clue clue modified the milestones: v0.8.0, v1.1.0 Apr 23, 2017
@andig
Copy link
Contributor

andig commented Oct 2, 2017

Checking back here. It seems UDS Connector has meanwhile been merged, but UDS Server still seems missing. It might also make sense to enhance Server to create the underlying UDS/TCP/Secure server according to URI instead of proxying a TcpServer?

@clue
Copy link
Member Author

clue commented Oct 2, 2017

@andig Correct 👍 We're currently focusing our efforts on the HTTP component and on stabilizing things, but in the meantime I suppose we would be super happy to accept new feature PRs 👍

@clue
Copy link
Member Author

clue commented Nov 13, 2017

This feature was originally planned for the v1.1.0 release milestone, but given the awesome PR #25 by @andig, it's safe to get this in with the next v0.8.6 release already :shipit: 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants