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

JSON Neo Tokio 0.2 #582

Closed
workingjubilee opened this issue Sep 3, 2020 · 1 comment · Fixed by #603
Closed

JSON Neo Tokio 0.2 #582

workingjubilee opened this issue Sep 3, 2020 · 1 comment · Fixed by #603

Comments

@workingjubilee
Copy link

tokio 0.2 has a lot of pertinent updates for IPC. #485 appears to still be in-progress which is obviously blocking, but it would be good to know if there are any additional requirements beyond that before jsonrpc-* can move to a ^0.2 version of tokio. Feel free to close this issue if the answer is "The moment #485 closes, tokio 0.2 is also ready" or "No plans to make that available, please move to jsonrpsee."

@tomusdrw
Copy link
Contributor

tomusdrw commented Sep 8, 2020

I don't see any obstacles to tokio-0.2 migration, I was considering it would be part of #485. That said, we don't currently have anyone actively working on migrating the transports due to lack of time. The jsonrpc vs jsonrpsee decision is yet to be made as well, so I unfortunately can't commit to anything. However jsonrpc, is a community project and I really hope that it can transcend paritytech's use of it.

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

Successfully merging a pull request may close this issue.

2 participants