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
It would be great if one could disconnect the HeadlessService.
🎤 Why is this feature needed ?
When the network connection is gone (e.g. b/c the app is running on a mobile with connectivity issues), the HeadlessService constantly attempts to reconnect. This is pointlessly straining the mobile's battery.
✌️ How do you aim to achieve this?
When I lose the connection, I want to tell the HeadlessServer to disconnect or yield its reconnection attempt until the connection is back.
🔄️ Additional Information
Alternatively, some more settings for the connection behavior (which comes down to socket.io, if I understand correctly) or a direct access to the underlying connection would help.
👀 Have you spent some time to check if this feature request has been raised before?
If it's just about exposing the underlying connection, I can do that. For more a more elaborate approach, I think I'ld need some decision on how this should be solved (e.g. by settings or a disconnection method?) before tending to it.
The text was updated successfully, but these errors were encountered:
🔖 Feature description
It would be great if one could disconnect the
HeadlessService
.🎤 Why is this feature needed ?
When the network connection is gone (e.g. b/c the app is running on a mobile with connectivity issues), the
HeadlessService
constantly attempts to reconnect. This is pointlessly straining the mobile's battery.✌️ How do you aim to achieve this?
When I lose the connection, I want to tell the
HeadlessServer
to disconnect or yield its reconnection attempt until the connection is back.🔄️ Additional Information
Alternatively, some more settings for the connection behavior (which comes down to
socket.io
, if I understand correctly) or a direct access to the underlying connection would help.👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
If it's just about exposing the underlying connection, I can do that. For more a more elaborate approach, I think I'ld need some decision on how this should be solved (e.g. by settings or a disconnection method?) before tending to it.
The text was updated successfully, but these errors were encountered: