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
When launching a server, all plugins' losc:open() functions create an infinite loop without any way to exit it via code. Instead a user must forcefully terminate the lua runtime. This makes the server functionality impossible to embed in more complex applications.
A solution would be to enforce a 'non-blocking' requirement on each plugin and adapt the high-level api as necessary (see #32). Backwards compatibility with existing 'blocking' usages could be accomplished by adding a default blocking=true param to the losc:open() function
The text was updated successfully, but these errors were encountered:
Yes, the plugins included are more or less "examples" on implementation and could definitely be improved for more use-cases. My original idea was that it would be up to the plugin if it would block or not on losc:open(), the function signature can vary depending on the plugin implementation so a blocking flag could be implemented for a specific plugin.
When launching a server, all plugins'
losc:open()
functions create an infinite loop without any way to exit it via code. Instead a user must forcefully terminate the lua runtime. This makes the server functionality impossible to embed in more complex applications.A solution would be to enforce a 'non-blocking' requirement on each plugin and adapt the high-level api as necessary (see #32). Backwards compatibility with existing 'blocking' usages could be accomplished by adding a default
blocking=true
param to thelosc:open()
functionThe text was updated successfully, but these errors were encountered: