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

Server life cycle... #5

Open
voneddy opened this issue May 4, 2016 · 1 comment
Open

Server life cycle... #5

voneddy opened this issue May 4, 2016 · 1 comment
Labels

Comments

@voneddy
Copy link

voneddy commented May 4, 2016

Hi just a quick question, you say 'the server stops responding when the view is terminated / destroyed', is that actual shutting down of the app? Or just when the use hits home (etc)?

Just wondering if the app is still open but the user has navigated away from it if the server will still respond? I'm trying to display info to the user via web sockets when the user has navigated away from the app and assessing my options...

Cheers

@becvert
Copy link
Owner

becvert commented May 5, 2016

The server is destroyed on actual shutdown of the App. It does not survive as a background service.
When the app is running in the background, it should work ok.
When the app (activity) is paused it may not receive messages or accept new connections, but on resume it's back to normal, and previously connected sockets still are, normally.
I think that's more accurate like that.

The Home button may pause or not the app, I think it depends on the platform.

I should probably review the description in the README.

Tell me if the behaviour is actually otherwise. Thanks

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

No branches or pull requests

2 participants