You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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 dedicatedndn-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.
The text was updated successfully, but these errors were encountered: