-
Notifications
You must be signed in to change notification settings - Fork 26
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
Refresh on open #82
Comments
That means, the newly spawned server would have to know of this tab somehow. Any idea on how to do this? Doing it from the client side could also be an option. E.g. upon detection that the connection to the server is lost, it could regularly check for a new server to get a new version of the page. |
Ha thanks for answering (and hi!, I'll be in Zurich around the 18th 😝 ), I have no idea and was hoping you would 🙈 . I reckon it's not a super important issue but would be cool. I reckon client side makes more sense (?) by reviewing tabs or something, not sure how that can be done. |
Would have to get into the whole thing again -- no idea how we implemented it in detail back then 😉 Agree, I don't see any option how the newly spawned server should know of any running clients. But the clients can just try to connect to the same server (localhost, same port) again... Yeah, busy times here. Will check tomorrow if I happen to be around Zurich for work on the 18th. Probably not... the offer with BBQ and beers near Lake Constance is still on though 😉 |
This would probably be solved by #23 |
If a tab is already opened at
localhost:...
and the server is (re)started, that tab should be refreshed.The text was updated successfully, but these errors were encountered: