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
go pion and libdatachannel both emit events synchronously. To move into the async world without potentially filling up memory with messages we had implemented "slow app timeouts" in the go integration, but also with some tokio timeout wrappers on app-side handling functions.
A simpler solution that is more resilient to momentary cpu pauses would be to just use a bounded channel and close the connection if we cannot send to the channel. This has been implemented in the experimental libdatachannel backend.
This should also be implemented for the go pion integration, and the timeout wrappers in app logic should be removed.
The text was updated successfully, but these errors were encountered:
go pion and libdatachannel both emit events synchronously. To move into the async world without potentially filling up memory with messages we had implemented "slow app timeouts" in the go integration, but also with some tokio timeout wrappers on app-side handling functions.
A simpler solution that is more resilient to momentary cpu pauses would be to just use a bounded channel and close the connection if we cannot send to the channel. This has been implemented in the experimental libdatachannel backend.
This should also be implemented for the go pion integration, and the timeout wrappers in app logic should be removed.
The text was updated successfully, but these errors were encountered: