-
Notifications
You must be signed in to change notification settings - Fork 280
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
Backport event loop support from usrsctp-neat #292
Comments
PRs welcome! :) |
PR does exist: #38. It was just discarded because "Support for external event loop is being worked on in the NEAT fork or usrsctp to get some experience. This will be merged eventually." However usrsctp-neat is not active at all. |
AFAIK they are not entirely identical approaches but I don't actually care about which is being merged... obviously, it should be the better one. Speaking for myself, I guess one of the reasons why it takes so long is that #38 is huge and should be split up into small, digestible PRs. |
We'll do separate and specific PRs for both single-thread and GYP support. We'll fight them once done :) |
Is there any update on merging the changes of usrsctp-neat, or making libneat work with the upstream version of usrsctp? |
I'm not sure if anyone is working on neat right now... |
Hi, we forked usrsctp and added "single-thread" support. It's identical to PR #38 but does not include changes other than those to allow single thread operation: master...versatica:single-thread We are using it and works fine. Would you accept a PR? |
If it is a PR adding only that feature and not breaking backwards compatibility, I would love to integrate it. |
Great, will do it soon.
El mar., 6 ago. 2019 13:29, Michael Tüxen <notifications@github.com>
escribió:
… If it is a PR adding only that feature and not breaking backwards
compatibility, I would love to integrate it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#292?email_source=notifications&email_token=AAAD6P57VL4PPQE4QMHSDXDQDFOA5A5CNFSM4GPEDWR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3U2S5I#issuecomment-518629749>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAD6PZ3GDVH3JMBW6GCENDQDFOA5ANCNFSM4GPEDWRQ>
.
|
Yup. If there's anything missing, I'll reopen. |
Works well - thanks a lot! |
Would be the only thing left I need to be able to use the upstream usrsctp in RAWRTC. 🙂
The text was updated successfully, but these errors were encountered: