-
Notifications
You must be signed in to change notification settings - Fork 72
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 for Unix Domain Socket #1
base: master
Are you sure you want to change the base?
Conversation
this instead of msgpackrpc.transport.tcp for unix domain socket support.
Please ignore multiple comments reading the same content. Its a goofup with eclipse and Egit. |
In this weekend, I will check this pull request. |
Thanks. Let me know if you need any changes. |
I have serveral comments:
Please remove these comments on top of each file.
Please move USD usage to Example section, not top.
UDSADdress is not common name.
Please fix these bugs.
See following example. # OK
"""\
Foo
Bar
"""
# NG
"""Foo
Bar""" Please apply above changes. |
Thanks for your review. Will update and get back.
|
Well, any chance that this will be merged? |
Been a long time! I didn't think people would like to use unix domain Regards, On Sat, Feb 14, 2015 at 6:31 PM, Auke Willem Oosterhoff <
|
What happened with this merge? I would like to use it! :) |
This patch doesn't apply my reviews so I can't merge. |
Hi
I have forked the base repo and added support for Unix domain sockets. My main objective was as less intrusion as possible in the base code, and come up with something which can be 'plug and played'.
I have created a new transport builder (transport->uds.py) and a new address object msgpackrps->udsaddress.py. I have some examples demonstrating how to use UDS instead of tcp/ip sockets for msgpack rpc. Please review my repository and let me know if you are okay with merging these changes.