The front end of the session page can do nothing more than a session, cookie, url and traditional values, but the first two are stored locally, if it comes to interactive user A and user B, then the two devices, the need to address the url stitching parameters, to complete page sessions (without regard to traditional values VUE component framework)
Again relates to developing a first channel and a two-terminal micro-browser to pass the value applied to the embodiment of this splicing url parameters, but after completion of splicing, the rear end of said feedback is given, it reported a wrong type, the type of the error The reaction is to use JSON.stringify () methods to render the format, but after the translation error,
So I went to the back-end print a moment pass past values (id = 25% 67% 87% * & ......) but the micro-channel test developer tools on your PC, transfer the past is (id = 25) completely no error
Later tests found in micro-channel transmission of the real machine, micro-channel will themselves add something of his own judgment parameters and the like in the url address, so the process url taken in carrying out needed this period of re-use of regular Spilled or () method of secondary interception