JavaScript use solves cross-domain problems

In order for the web server to implement, the server should only look for whether the request contains the windowname parameter. If the windowname parameter is included, the server should return an HTML document with the string value set, respond to the request and pass it to the client. For example:
/?windowname=true

If the server wants to respond to the client with Hello, it should return an HTML page:



It can also be converted to JSON data:


If you create a resource manually, writing a large number of multi-line JSON objects as a referenced string should be difficult and prone to errors. You can simply create JSON data using HTML samples like this, which will be converted to a JSON string without manually escaping JSON to a string:


Similarly, if you want to pass HTML/XML data, here is a sample implementation without manually converting this data into strings:


Some advantages of transmission technology over other cross-domain transmission:

It is safe. That is, it is as secure as other secure transport-based frames, such as Fragment Identifier messaging (FIM) and Subspace. (I)Frames also have their own security issues, since frames can change the location of other frames, but this is a very different security overflow and is usually less severe.
It's faster than FIM because it doesn't have to deal with small packet size Fragment Identifiers, and it won't have more "machine gun" sound effects on IE. It is also faster than Subspace, which requires loading two Iframes and two local HTML files to handle a request. Only an Iframe and a local file are required.
It is simpler and safer than FIM and Subspace. FIM is slightly complex, while Subspace is very complex. Subspace also has some additional restrictions and installation requirements, such as pre-declaring all target hosts and having DNS portals for several different special hosts. Very simple and easy to use.
It does not require any plugins (such as Flash) or alternative technologies (such as Java).