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

Backport event loop support from usrsctp-neat #292

Closed
lgrahl opened this issue Jan 10, 2019 · 14 comments
Closed

Backport event loop support from usrsctp-neat #292

lgrahl opened this issue Jan 10, 2019 · 14 comments

Comments

@lgrahl
Copy link
Contributor

lgrahl commented Jan 10, 2019

Would be the only thing left I need to be able to use the upstream usrsctp in RAWRTC. 🙂

@weinrank
Copy link
Contributor

PRs welcome! :)

@ibc
Copy link

ibc commented Jun 24, 2019

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.

@lgrahl
Copy link
Contributor Author

lgrahl commented Jun 24, 2019

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.

@lgrahl
Copy link
Contributor Author

lgrahl commented Jun 24, 2019

Maybe you should talk to @tuexen and @weinrank on how to approach the issue of backlogged PRs. Luckily, #300 is not a pressing issue for me... at least before this issue has been resolved.

@ibc
Copy link

ibc commented Jun 24, 2019

We'll do separate and specific PRs for both single-thread and GYP support. We'll fight them once done :)

@dreibh
Copy link
Contributor

dreibh commented Aug 6, 2019

Is there any update on merging the changes of usrsctp-neat, or making libneat work with the upstream version of usrsctp?

@tuexen
Copy link
Member

tuexen commented Aug 6, 2019

I'm not sure if anyone is working on neat right now...

@ibc
Copy link

ibc commented Aug 6, 2019

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?

@tuexen
Copy link
Member

tuexen commented Aug 6, 2019

If it is a PR adding only that feature and not breaking backwards compatibility, I would love to integrate it.

@ibc
Copy link

ibc commented Aug 6, 2019 via email

@jmillan
Copy link
Contributor

jmillan commented Aug 7, 2019

@tuexen,

Please find the PR #339 synchronised with master branch. It's essentially a cleanup of #38 with everything filtered but the the single thread implementation.

I can squash the commits into a single one if you like.

@tuexen
Copy link
Member

tuexen commented Aug 13, 2019

@lgrahl Can this be closed since we have f6aa4b0 in the master tree now?

@lgrahl
Copy link
Contributor Author

lgrahl commented Aug 13, 2019

Yup. If there's anything missing, I'll reopen.

@lgrahl lgrahl closed this as completed Aug 13, 2019
@lgrahl
Copy link
Contributor Author

lgrahl commented Aug 15, 2019

Works well - thanks a lot!

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

6 participants