-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
Support Unix domain sockets. #4046
Comments
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. If no further activity occurs, it might be closed. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
|
@PierceNg Still relevant? |
On Mon, Apr 06, 2020 at 05:20:35AM -0700, Astares wrote:
@PierceNg Still relevant?
Yes, still relevant. I'll get the code ready this month or close it if I
cannot.
|
Hi pierceNG You can also ask the consortium guys for help. S. |
It's not clear to me if the code finally arrived or not. |
There was already some degree of support, but as seen in this blog post a few more changes were required: https://samadhiweb.com/blog/2013.07.27.unixdomainsockets.html fixes pharo-project#4046
I was not aware of this issue (sorry), but we (@JurajKubelka and me) recently added some support for Unix Domain Sockets to the Zinc HTTP Components project and got the client side working, but got stuck on the server side part which we wanted to be able to write unit tests. There is a new package https://github.com/svenvc/zinc/tree/master/repository/Zinc-HTTP-UnixSocket.package You can check some of our commits from Aug 30 https://github.com/svenvc/zinc/commits/master or some of the closed PRs https://github.com/svenvc/zinc/pulls?q=is%3Apr+is%3Aclosed which contain conversations about this subject. |
The socket plugin already supports Unix domain sockets. I have code for Pharo 2.0 that I will adapt to current Pharo.
The text was updated successfully, but these errors were encountered: