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

Non-nng client communicating with nng server? #91

Open
chebee7i opened this issue Oct 1, 2021 · 2 comments
Open

Non-nng client communicating with nng server? #91

chebee7i opened this issue Oct 1, 2021 · 2 comments

Comments

@chebee7i
Copy link

chebee7i commented Oct 1, 2021

I have a server running with trio and pynng. It would normally be using Rep0 and expecting to communicate with Req0.

However, some of my clients are unable to run pynng. I am wondering if it is possible (without a lot of extra work) for them to send the necessary info over to the server and get a response.

I'd guess that this is not possible. Do you have any other suggestions for how to achieve this sort of communication? Some of the clients are, unfortunately, still in Python 2 for a bit longer.

@chebee7i
Copy link
Author

chebee7i commented Oct 1, 2021

@codypiersall
Copy link
Owner

Check out https://github.com/tonysimpson/nanomsg-python —-the API is different and it uses the legacy nanomsg library, but I believe it does still work with Python 2.7.

If you're feeling rather bold and ambitious, a pure-Python solution is possible; I outlined a hacky version in an answer on Stack Overflow. To do it right would require quite a bit of work in pure Python, but sometimes hacks are good enough.

If you can get nanomsg-python to work though that's what I would go with.

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

No branches or pull requests

2 participants