Auto reconnect to a zetta server from browser by URL

[13protons]

While developing for zetta (an app or driver), the zetta browser constantly looses it's link to my local zetta server.

How to reproduce:

• run zetta locally
• point the zetta browser to it
• shut down your local zetta, then restart to use your updated code
• Now the zetta browser is frozen, because it lost it's link to your local zetta server

If the browser attempts to reconnect when the zetta server comes back up, It appears that it's doing it based on the server ID (which changes), rather than the URL (which doesn't). Better behavior would be to auto-reconnect by url, saving the user from having to refresh the zetta browser during each code/save/reload cycle.

[AdamMagaluk]

This is caused by the url's being generated by the server's id which is generated at startup. In some refactoring I did yesterday here it will no longer generate unique ids for the servers.

The new way of addressing the server through the api is based on the servers name. Which does not change after you restart. After the PR is merged you will only have to refresh the page.

[13protons]

If I understand you correctly, you’re saying the mechanism is now in place an this can be built as a feature in the browser?

—
Alan Languirand

On Fri, Oct 10, 2014 at 1:32 PM, Adam Magaluk [email protected]
wrote:

This is caused by the url's being generated by the server's id which is generated at startup. In some refactoring I did yesterday here it will no longer generate unique ids for the servers.

The new way of addressing the server through the api is based on the servers name. Which does not change after you restart. After the PR is merged you will only have to refresh the page.

Reply to this email directly or view it on GitHub:
#8 (comment)