Can we make URLs to Zetta browser servers prettier?

[landlessness]

can we sprinkle some sugar on the Zetta browser URLs so they are ... prettier?

These are rough on the eyes:

http://browser.zettajs.io/#/overview?url=http:%2F%2Fhello-zetta.herokuapp.com

http://browser.zettajs.io/#/device?url=http:%2F%2Fhello-zetta.herokuapp.com%2Fservers%2Fbeaglebone%2Fdevices%2Fa153df48-cd1a-4a36-ab82-fb0e16b3b65e

Something like this possible?

http://browser.zettajs.io/hello-zetta.herokuapp.com

http://browser.zettajs.io/hello-zetta.herokuapp.com/servers/beaglebone/devices/a153df48-cd1a-4a36-ab82-fb0e16b3b65e

[kevinswiber]

The URL looks this way so that a) we can keep the client browser side and
b) client application state is addressable.

While the URLs may be ugly, we do get benefits sacrificed by most
single-page apps.

Sent from my iPhone

On Oct 19, 2014, at 12:16 AM, brian mulloy [email protected] wrote:

can we sprinkle some sugar on the Zetta browser URLs so they are ...
prettier?

These are rough on the eyes:

http://browser.zettajs.io/#/overview?url=http:%2F%2Fhello-zetta.herokuapp.com

http://browser.zettajs.io/#/device?url=http:%2F%2Fhello-zetta.herokuapp.com%2Fservers%2Fbeaglebone%2Fdevices%2Fa153df48-cd1a-4a36-ab82-fb0e16b3b65e

Something like this possible?

http://browser.zettajs.io/hello-zetta.herokuapp.com

http://browser.zettajs.io/hello-zetta.herokuapp.com/servers/beaglebone/devices/a153df48-cd1a-4a36-ab82-fb0e16b3b65e

—
Reply to this email directly or view it on GitHub
#15.

[landlessness]

In your reply:

I'm not getting a). Was that an incomplete thought / typo? was it about being loosely coupled from the server?

b) I get.

c) Is there also a constraint that ZB should be a single page app? Is that better for hypermedia API consumption?

Sent from my iPhone

On Oct 19, 2014, at 12:28 AM, Kevin Swiber [email protected] wrote:

The URL looks this way so that a) we can keep the client browser side and
b) client application state is addressable.

While the URLs may be ugly, we do get benefits sacrificed by most
single-page apps.

Sent from my iPhone

On Oct 19, 2014, at 12:16 AM, brian mulloy [email protected] wrote:

can we sprinkle some sugar on the Zetta browser URLs so they are ...
prettier?

These are rough on the eyes:

http://browser.zettajs.io/#/overview?url=http:%2F%2Fhello-zetta.herokuapp.com

http://browser.zettajs.io/#/device?url=http:%2F%2Fhello-zetta.herokuapp.com%2Fservers%2Fbeaglebone%2Fdevices%2Fa153df48-cd1a-4a36-ab82-fb0e16b3b65e

Something like this possible?

http://browser.zettajs.io/hello-zetta.herokuapp.com

http://browser.zettajs.io/hello-zetta.herokuapp.com/servers/beaglebone/devices/a153df48-cd1a-4a36-ab82-fb0e16b3b65e

—
Reply to this email directly or view it on GitHub
#15.
—
Reply to this email directly or view it on GitHub.

[13protons]

Someone correct me if I'mnot expressing this the right way, but I think the value of the single page app comes in the form of web socket values not needing to make a round trip to a backend server when monitoring local zetta instances. 

Aka, the browser is for dev, and single page makes it much faster for dev with a local zetta server. 

You can see an example of this difference/latency when running through the hello world project. Compare the resolution of the sine wave show page when viewed locally vs. when your server is peering to the hello-zetta.herokuapp.com zetta instance.

On Sun, Oct 19, 2014 at 4:46 AM, brian mulloy [email protected]
wrote:

In your reply:
I'm not getting a). Was that an incomplete thought / typo? was it about being loosely coupled from the server?
b) I get.
c) Is there also a constraint that ZB should be a single page app? Is that better for hypermedia API consumption?
Sent from my iPhone

On Oct 19, 2014, at 12:28 AM, Kevin Swiber [email protected] wrote:

The URL looks this way so that a) we can keep the client browser side and
b) client application state is addressable.

While the URLs may be ugly, we do get benefits sacrificed by most
single-page apps.

Sent from my iPhone

On Oct 19, 2014, at 12:16 AM, brian mulloy [email protected] wrote:

can we sprinkle some sugar on the Zetta browser URLs so they are ...
prettier?

These are rough on the eyes:

http://browser.zettajs.io/#/overview?url=http:%2F%2Fhello-zetta.herokuapp.com

http://browser.zettajs.io/#/device?url=http:%2F%2Fhello-zetta.herokuapp.com%2Fservers%2Fbeaglebone%2Fdevices%2Fa153df48-cd1a-4a36-ab82-fb0e16b3b65e

Something like this possible?

http://browser.zettajs.io/hello-zetta.herokuapp.com

http://browser.zettajs.io/hello-zetta.herokuapp.com/servers/beaglebone/devices/a153df48-cd1a-4a36-ab82-fb0e16b3b65e

—
Reply to this email directly or view it on GitHub
#15.
—

Reply to this email directly or view it on GitHub.

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