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

NDN-lite main event loop vs. dedicated thread #1

Open
cgundogan opened this issue Feb 10, 2020 · 2 comments
Open

NDN-lite main event loop vs. dedicated thread #1

cgundogan opened this issue Feb 10, 2020 · 2 comments
Labels
question Further information is requested

Comments

@cgundogan
Copy link
Member

In the current implementation, ndn-lite relies on an event loop in the main application (e.g., here). A more suitable way in RIOT is to create a dedicated ndn-lite thread that runs the process manager and frees the main thread to be used by the user application.

Was there a specific design decision for not using a dedicated thread?

@yan-foto initially encountered this issue.

@cgundogan cgundogan added the question Further information is requested label Feb 10, 2020
@cgundogan
Copy link
Member Author

Any ideas on how to proceed here, @RoySCU ?

@tianyuan129
Copy link
Member

tianyuan129 commented Jun 25, 2020

I agree this is a more suitable way for RIOT application and also openthread and ndn-riot were packaged in this way (if I remember correctly).

We did not using a dedicated thread for trying to keep the same style with other environment's implementation (e.g., POSIX). But I indeed agree switching to a dedicated thread is more suitable here.

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

No branches or pull requests

2 participants