Discuss about introducing Ajax InPage Resource Locator

First of all, I made Ajax InPage Resource Locator, the main meaning is to add a part of QueryString to indicate the specific location of a content in the Ajax page (it can also be considered as the user's Operation Records on the page ).

Why should we introduce such a thing?

Let's open a typical Ajax page, such as the Asp.net Ajax homepage, and click "Get Started" above. In this process, the address bar of the browser has not changed, but the specific content has changed, this will bring a lot of difficulties to the user's communication/collection, far from being convenient when a URL does not use Ajax. Think about this situation: you have found a good thing and want to share it with your friends. But after sending a link, you have to tell him, "Click here first, double-click it, wait a few seconds, then click ", isn't it very troublesome?

It is not only communication between users, but also a great deal of trouble when search engines and other programs encounter Ajax. There is a lot of content on the Web pages that use Ajax. If the Web Server does not Post (or run JavaScript), it is impossible for the search engine to see it, but if you Post (or run JavaScript) casually ), it may have a strange influence-you don't want your e-commerce website to be placed by search engines on a daily basis?

If you use one method to assign an identifier to the content that cannot be located by URL on the Ajax page, we can avoid these problems.

For example, assign the following URL to the content we mentioned above: http://ajax.asp.net/Default.aspx? & GetStarted, and then use other methods to solve these problems. & GetStarted here is what I call Ajax InPage Resource Locator.

The above & (the specific strings can be discussed here as an example) is used to tell the Server-side program that GetStarted is used to locate the content inside the page, the server can return the correct content;
With a URL that can directly locate the content, we can provide more precise functions such as "share the content on this page" and "add to Favorites" on the page;
For search engines, we can use a technology similar to the Google search result page: before a user operates, the Href of the link is a normal http url, and it becomes another (such as javascript: __dopostback ...). In this way, we can not only get better SEO, but also improve the compatibility with browsers (javascript browsers are also supported ).

What do you think I think?

In addition, I think this technology can be used not only for Ajax pages, but also for general pages such as Asp.net that require PostBack.

In fact, PostBack/Ajax is used for "user interaction" rather than "information publishing". In the former, there is no need for a URL to locate a step/action. But the reality is that many systems used for "information publishing" also use these PostBack/Ajax technologies. Who can simply blame the people who have done this wrong?