That is notncorrect. GUID is only preserved within one single page. Go to the example, create a page. Copy the link and open in a new tab. You will see.

The use of temporary GUIDs might be ok when those are used INTERNALLY only and not exposed outside.

What happens with Spine, though, is that those IDs are used in a URL.

So in the example I get the URL for the newly created page: http://spine-rails3.herokuapp.com/#/pages/34B3CC88-32CC-4D08...

Who of you can actually access it?

That isn't right. The GUIDs should be internal only.

This leads us to the complexity of the "Async" UI in general. In order to redirect (navigate) user to a proper URL you DO need to wait for the response from the server.

But the real async UI should just allow user to do something else. It doesn't mean it should not WAIT for the server response.

I wonder what was the reason behind this?