CN112783548B - Access method and device of network system - Google Patents
Access method and device of network system Download PDFInfo
- Publication number
- CN112783548B CN112783548B CN201911096823.8A CN201911096823A CN112783548B CN 112783548 B CN112783548 B CN 112783548B CN 201911096823 A CN201911096823 A CN 201911096823A CN 112783548 B CN112783548 B CN 112783548B
- Authority
- CN
- China
- Prior art keywords
- network system
- page
- url
- version network
- new version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000006870 function Effects 0.000 claims description 32
- 238000013507 mapping Methods 0.000 claims description 12
- 238000012544 monitoring process Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 11
- 239000012634 fragment Substances 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
One or more embodiments of the present disclosure provide a method and an apparatus for accessing a network system, where the method may include: acquiring page data of a new version network system; and loading a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a method and an apparatus for accessing a network system.
Background
A network system (i.e., a web system) may be understood as an application accessed through a network. And the user can browse and operate the network system by interacting with the server through the browser. In the related art, there are generally two ways of access to a network system:
the new version network system completely covers the old version network system. After the developer completes the development of the new version network system, the old version network system is completely replaced by the new version network system.
And the new and the old version network systems coexist. The new version network system and the old version network system are independent and coexist, and a user can actively switch between the two systems.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a method and apparatus for accessing a network system.
In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present disclosure, there is provided a method for accessing a network system, including:
acquiring page data of a new version network system;
and loading a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page.
According to a second aspect of one or more embodiments of the present specification, there is provided an access method for a network system, including:
adding a mark in an access request aiming at a network system URL, wherein the mark comprises a first mark used for indicating that an access target is a new version network system corresponding to the network system URL or a second mark used for indicating that the access target is an old version network system corresponding to the network system URL;
sending the access request to a server, and enabling the server to return first page data for loading the new version network system according to the first mark or return second page data for loading the old version network system according to the second mark;
Analyzing the first page data to load the page corresponding to the new version network system, or analyzing the second page data to load the page corresponding to the old version network system.
According to a third aspect of one or more embodiments of the present specification, there is provided an access device of a network system, including:
the acquisition unit acquires page data of the new version network system;
and the loading unit loads a parent page corresponding to the new version network system by analyzing the page data, and a child page corresponding to the old version network system is embedded in the parent page.
According to a fourth aspect of one or more embodiments of the present specification, there is provided an access device of a network system, including:
an adding unit for adding a mark in an access request aiming at a network system URL, wherein the mark comprises a first mark used for indicating that an access target is a new version network system corresponding to the network system URL or a second mark used for indicating that the access target is an old version network system corresponding to the network system URL;
the sending unit sends the access request to a server, so that the server returns first page data for loading the new version network system according to the first mark or returns second page data for loading the old version network system according to the second mark;
And the loading unit analyzes the first page data to load the page corresponding to the new version network system or analyzes the second page data to load the page corresponding to the old version network system.
According to a fifth aspect of one or more embodiments of the present specification, there is provided an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of the first or second aspect by executing the executable instructions.
According to a sixth aspect of one or more embodiments of the present description, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to the first or second aspect.
Drawings
Fig. 1 is a schematic view of a scenario in which an upgrade network system is provided in an exemplary embodiment.
Fig. 2 is a flowchart of a method for accessing a network system according to an exemplary embodiment.
FIG. 3 is a schematic diagram of interactions between a browser and a server according to an exemplary embodiment.
Fig. 4 is a schematic diagram of a page of a new version of the network system according to an exemplary embodiment.
FIG. 5 is a schematic diagram of a page nest presentation provided by an exemplary embodiment.
FIG. 6 is a schematic diagram of a matching linkage between a parent page and a child page provided by an example embodiment.
Fig. 7 is a flowchart of another method for accessing a network system according to an exemplary embodiment.
Fig. 8 is a schematic diagram of an apparatus according to an exemplary embodiment.
Fig. 9 is a block diagram of an access apparatus of a network system according to an exemplary embodiment.
Fig. 10 is a block diagram of an access apparatus of another network system provided by an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
Fig. 1 is a schematic view of a scenario in which an upgrade network system is provided in an exemplary embodiment. As shown in fig. 1, the system may include a server 11, a network 12, several electronic devices, such as a cell phone 13, a PC14, and so on.
The server 11 may be a physical server comprising a separate host, or the server 11 may be a virtual server carried by a cluster of hosts. The server 11 is used for maintaining the application functions and data of the network system, and performing function expansion and version update for the network system.
The handset 13, PC14, etc. are just some types of electronic devices that can be used by a user. Indeed, it is obvious that the user may also use electronic devices of the type such as: tablet devices, notebook computers, palm top computers (PDAs, personal Digital Assistants), wearable devices (e.g., smart glasses, smart watches, etc.), etc., as one or more embodiments of the present description are not limited in this regard. The electronic device is provided with a browser, and an access request can be initiated to the server 11 through the browser, so that the network system can be accessed.
The network 12 for interaction between the electronic device such as the mobile phone 13 and the PC14 and the server 11 may include various types of wired or wireless networks.
The network system upgrading scheme of the present specification is described below with reference to an embodiment, and smooth transition between new and old versions of a network system can be achieved in the upgrading process.
Fig. 2 is a flowchart of a method for accessing a network system according to an exemplary embodiment. As shown in fig. 2, the method applied to the electronic device may include the following steps:
step 202, obtaining page data of a new version network system.
By inputting the URL of the new version network system in the browser of the electronic device, the browser can initiate an access request for the new version network system to the server, and receive page data returned by the server, wherein the page data can be an html format document.
The URL of the new version of the network system may be manually entered by the user in the address bar of the browser; alternatively, the user may trigger a link, icon, etc. corresponding to the URL without manual input; alternatively, the URL of the new version network system may be obtained and accessed in other manners, which is not limited in this specification.
And 204, loading a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page.
By taking the page corresponding to the new version network system as the parent page and taking the page corresponding to the old version network system as the child page, the child page is embedded into the parent page, so that at least one part of functions of the old version network system can still be used in the process of upgrading the version of the network system instead of completely discarding the old version network system, on one hand, the new version network system can be started on the morning without waiting for complete development, thereby avoiding a lengthy development period, on the other hand, the defect of the new version network system can be avoided to cause the complete unavailability of the system, and the normal use of users (especially old users who are accustomed to using the old version network system) can be prevented from being influenced due to overlarge change of the new and old version network system, and the learning cost of the users is reduced. Meanwhile, the user can view the page content of the parent page and the child page in the same page and use related functions, which is equivalent to accessing one network system for the user, but does not feel that the user accesses two network systems respectively, and does not need to switch between different network systems, so that the method has extremely high uniformity.
According to the function development progress of the new version network system, the function proportion occupied by the old version network system in the new version network system can be adjusted at will. In general, the proportion of the old version network system is relatively large in the early stage of version update (in extreme cases, the new version network system can only provide a shell, all functions are provided by the old version network system), and with the continuous development and perfection of the new version network system, the proportion of the old version network system can be gradually reduced until the old version network system is completely removed, so that the network system is completely updated. In other words, based on the technical scheme of the specification, gradual updating and smooth transition of the network system can be realized, and the network system can be adjusted to be an old-version network system at any time under the condition that the new-version network system is unstable or unavailable, so that the network system has extremely high reliability.
The page nesting between the new version network system and the old version network system can be achieved in various ways. For example, by including an iframe tag in page data of the new version network system, the iframe tag records a URL of the old version network system, for example, the URL may be recorded in an "src" attribute of the iframe tag, so that a browser may embed and display a child page of the old version network system in a parent page of the new version network system by parsing the content of the iframe tag.
The new and old versions of the network system may employ different URLs. For example, the URL of the new version network system may be http:// xxx/b.html, and the URL of the old version network system may be http:// xxx/a.html, so that when the browser accesses a different URL, a different access request may be initiated to the server, and the server may return corresponding page data to the browser according to the access request. For example, when the URL accessed by the browser is http:// xxx/b.html, the server returns page data of the new version network system, so that the browser can analyze and load a parent page corresponding to the new version network system; when the URL accessed by the browser is http:// xxx/a.html, the server returns page data of the old version network system, so that the browser can analyze and record a child level page corresponding to the old version network system, and the child level page is embedded into the parent level page.
The network systems of the new and old versions may employ the same URL. Then, the version update of the network system does not require the user to learn and record a new URL, thereby avoiding increasing the use cost of the user. While for the server it is necessary to identify the actual intent of the browser, whether it is desired to access a new version of the network system or to embed an old version of the network system in order to return the appropriate page data. For example, when a user initiates an access request for a URL by entering the URL in an address bar or clicking on a link, icon, etc., the browser may determine that the access request is an external request (relative to an internal request from a parent page); when the access request is initiated during the process of parsing the page data of the parent page, for example, to the URL included in the iframe tag, the browser may determine that the access request is an internal request. Then the browser may flag the access request to indicate that the access request is an external request or an internal request; for example, a special field may be added in the http header, which indicates that the corresponding access request is an internal request. Accordingly, after sending the marked access request to the server, the server may determine whether to be an external request or an internal request by parsing the mark in the access request; for example, when the server parses the http header without the special field, it may be determined that the access request is an external request, page data applied to the load parent page may be returned, and when the server parses the http header with the special field, it may be determined that the access request is an internal request, page data applied to the load child page may be returned. Therefore, through cooperation between the browser and the server, even if the network systems of the new version and the old version adopt the same URL, the server can still successfully identify the access intention of the browser and properly return corresponding page data.
After the browser analyzes the page data returned by the server, the default loaded parent page may be irrelevant to the old version network system, and may not temporarily display the content related to the child page. Wherein, the parent page can contain a plurality of function options, and the function options are used for adjusting the display content of the parent page; when the selected function option is related to the old version network system, the child level page can be nested and loaded in the parent level page, and the page data corresponding to the child level page can be temporarily acquired, analyzed and loaded, or the page data corresponding to the child level page can be temporarily analyzed and loaded in advance.
Of course, in some cases, the default loaded parent page may be related to the old version network system, which is equivalent to that the default selects the function option related to the old version network system, and then the browser may automatically embed and display the child page corresponding to the old version network system in the parent page.
And the message passing which can cross windows is realized between the parent page and the child page, so that the collaboration between the new version network system and the old version network system is realized. Specifically, a route mapping table item between the URL of the new version network system and the URL of the old version network system can be established; and then, monitoring the message transmitted between the parent page and the child page, and updating the URL of the message receiver according to the routing mapping table item when the monitored message content shows that the URL of the message sender is changed by the segment identifier. For example, when the URL of the parent page changes with the segment identifier, the parent page may transmit a message to the child page, so that the URL of the child page generates a corresponding update; when the URL of the child level page changes with the fragment identifier, the child level page may pass a message to the parent level page so that the URL of the parent level page generates a corresponding update. For example, when the network system adopts the html5 protocol, the parent page or the child page may monitor whether the corresponding URL of the parent page or the child page is changed by using the hashChange (i.e. the # symbol in the URL and the following part of the URL), the message sender may implement message transmission between the parent page and the child page by using the PostMessage, and the message receiver may monitor the transmitted message by using the onmessage.
The network system in this specification may be a single page application (single page web application, SPA), i.e. all application functions exist in a single page that is not refreshed after loading, but rather exhibits logical preloading and relies on view switching in the content area (region) to exhibit content. Of course, the network system of the present specification may also employ a conventional architecture (not SPA).
The network system of the specification adopts a B/S (Browser/Server) network architecture, and a user can request the Server for access to the network system through a Browser running on the electronic equipment; accordingly, the developer only needs to develop and upgrade the network system at the server side without involving modification of the browser, so that the method is particularly suitable for smooth upgrade of the network system in the specification, and the user gradually transits from the old version network system to the new version network system under the condition of no perception.
FIG. 3 is a schematic diagram of interactions between a browser and a server according to an exemplary embodiment. As shown in fig. 3, the interaction process may include the steps of:
in step 301, the browser obtains the URL of the new version network system.
The user may enter the URL of the new version of the network system in the address bar of the browser. The URL of the new version of the network system may be the same as the URL of the old version of the network system so that the user does not need to change the recorded, used URL due to the version upgrade of the network system.
In step 302, the browser accesses the new version network system according to the acquired URL.
The browser initiates an access request for the URL to the server to access the new version of the network system. Since the new version network system is identical to the URL of the old version network system, it is necessary to ensure that the server can learn the access purpose of the browser to properly return the corresponding page data.
For example, when a URL is entered by a user in an address bar, the browser can determine that it needs to access itself for a new version of the network system, and thus can generate an access request in a manner in the related art without performing special processing. When the browser determines that the page data of the old version network system needs to be acquired, special processing needs to be implemented, for example, a special field is added in an http header of the access request to distinguish the situation.
Step 303, the server checks the http header of the access request; and when the special field is not contained, returning the html document of the new version network system to the browser.
As described above, the browser may choose whether to add a special field in the http header of the access request according to the actual situation. Accordingly, the server can determine the html document which the browser wants to obtain by checking the http header of the access request according to whether the special field is contained.
Step 304, the browser loads pages of the new version network system.
The browser can load pages of the new version network system by analyzing html documents returned by the server. For example, fig. 4 is a schematic page diagram of a new version of a network system according to an exemplary embodiment. As shown in fig. 4, a page 400 of a new version of the network system may include several areas, such as a navigation bar 401 at the top, a menu bar 402 on the left, an operation area 403 on the right, and so on. Assuming that the welcome page and the like shown in the navigation bar 401, the menu bar 402, and the operation area 403 are all developed elements in the new version network system, the browser can directly show the page 400 shown in fig. 4 based on the above-described html document corresponding to the new version network system, which elements are independent of the old version network system.
Step 305, detecting that a specific function is triggered, routing to the URL in the iframe tag.
In the menu bar 402 shown in fig. 4, several functional options such as application data, cluster management, monitoring center, log monitoring, etc. are included, and when the user selects different functional options, the display content of the operation area 403 can be controlled to change correspondingly.
The functions corresponding to these function options may exist in different situations: when the function is developed in the new version network system, the browser can display corresponding display content in the operation area 403 according to the html document corresponding to the new version network system returned by the server, which is consistent with the operation of the normal network system. And when the function is not developed in the new version network system, the support of the related function can be realized by adopting a mode of embedding the old version network system.
When the old version network system needs to be embedded, an html document corresponding to the new version network system can contain an iframe tag, and the src attribute of the iframe tag can be recorded with the URL of the old version network system; meanwhile, by establishing a routing mapping between the specific function and the iframe tag, when the function option corresponding to the specific function is triggered, the browser can route to the iframe tag and read the contained URL.
In step 306, a special field is added at the http header.
After the browser obtains the URL contained in the iframe tag, an access request can be initiated to the server aiming at the URL to request to obtain the html document corresponding to the old version network system, and the html document is used for being embedded into the page of the new version network system.
As described above, since the URL of the new version network system is the same as the URL of the old version network system, the browser needs to add a special field to the http header of the access request in step 306 to indicate that it needs to obtain the html document of the old version network system.
In step 307, the browser initiates an access request to the server.
Step 308, the server checks the http header of the access request; when the special field is contained, returning the html document of the old version network system to the browser.
In step 309, the browser embeds the page of the old version network system in the page of the new version network system.
The browser parses the html document returned by the server corresponding to the old version network system, and embeds the relevant page into the page of the new version network system loaded in step 304. The page loaded in the step 304 is called a parent page, and the page embedded in the step 309 is called a child page, so that nested display between the parent page and the child page is realized, and a user can view and operate the new version network system through the parent page or the old version network system through the child page.
For example, FIG. 5 is a schematic diagram of a page nest presentation provided by an exemplary embodiment. As shown in fig. 5, the function option "application data" contained in menu bar 402 may contain several sub-options, although this is not required. Assuming that the sub-option "user data" is triggered, the sub-option is routed to the iframe tag described above, so that the browser can obtain the html document of the old version network system via steps 306-309 and the like described above, thereby embedding the relevant page into the operation area 403 to replace the presentation content shown in fig. 4.
By embedding the page of the old version network system into the page of the new version network system, the user can view and operate the new and old version network systems in the same page. The parent-level page corresponding to the new version network system and the child-level page corresponding to the old version network system are not isolated from each other, but can realize cooperation linkage while nested display is realized. For example, FIG. 6 is a schematic diagram of a matching linkage between a parent page and a child page according to an exemplary embodiment. As shown in fig. 6, a routing mapping table entry between the URL of the parent page and the URL of the child page may be established in the routing mapping table, so as to implement association between the URL of the parent page and the URL of the child page.
Therefore, in the process of implementing the operation on the sub-level page by the user, the sub-level page can monitor that the fragment identifier of the sub-level page URL is changed through the hashChange event, so that the sub-level page can transmit a corresponding message to the parent level page through the PostMessage function to inform that the fragment identifier of the sub-level page URL is changed. Correspondingly, the parent page can receive the message sent by the child page in a mode of monitoring the onmessage function, and correspondingly change the fragment identifier of the parent page URL according to the routing mapping table item between the parent page URL and the child page URL, so that consistency between the parent page URL and the child page URL is maintained. Similarly, in the process that the user performs the operation on the parent page, the parent page can monitor that the fragment identifier of the parent page URL is changed through the hashChange event, and inform the child page based on the similar manner, so that the child page URL can be changed correspondingly, and accordingly consistency between the parent page URL and the child page URL is maintained, which is not described herein.
Fig. 7 is a flowchart of another method for accessing a network system according to an exemplary embodiment. As shown in fig. 7, the method applied to the electronic device may include the steps of:
And step 702, adding a mark in the access request aiming at the network system URL, wherein the mark comprises a first mark used for indicating that the access target is a new version network system corresponding to the network system URL or a second mark used for indicating that the access target is an old version network system corresponding to the network system URL.
By entering the web system URL (i.e., the URL of the web system) in the browser of the electronic device, the browser may initiate an access request to the web system to the server, and receive page data returned by the server, which may typically be an html format document. Wherein, the URL of the network system can be manually input in the address bar of the browser by a user; alternatively, the user may trigger a link, icon, etc. corresponding to the URL without manual input; alternatively, the URL of the network system may be obtained and accessed in other manners, which is not limited in this specification.
Step 704, sending the access request to a server, so that the server returns first page data for loading the new version network system according to the first mark, or returns second page data for loading the old version network system according to the second mark.
Step 706, parse the first page data to load the page corresponding to the new version network system, or parse the second page data to load the page corresponding to the old version network system.
In the case of a version update of a network system, if the URLs of the new and old versions are different, the user may indicate which version of the network system he wishes to access by initiating an access request to the different URL, and the server may also return the corresponding page data in a targeted manner. However, for some reasons, such as avoiding increasing the use cost of the user, the URL will not be changed when the version update occurs to the network system, that is, the URL of the new version and the old version of the network system are the same, so the browser may add a corresponding mark in the access request based on the access target of the user (that is, the network system desiring to access the new version or the old version), such as the first mark corresponding to the new version of the network system, the second mark corresponding to the old version of the network system, and the like, so the server can accurately return the corresponding page data according to the mark, so that the browser presents the corresponding page to the user.
In some cases, the new version network system and the old version network system may be independent from each other, and operations such as initiating an access request and displaying a page for the new version network system and the old version network system are also independent from each other. At this time, the browser may present the user with a plurality of options and determine which version of the network system the user wishes to access based on the options selected by the user.
In other cases, there may be a certain association between the new version network system and the old version network system, for example, the page corresponding to the new version network system may be displayed independently, while the page corresponding to the old version network system is displayed in a nested manner with the page of the new version network system, and specifically, a scheme such as the embodiment shown in fig. 2 may be adopted, that is, the page of the new version network system is used as a parent page, and the page of the old version network system is used as a child page and is embedded into the parent page. For example, when a user initiates an access request for a web system URL by entering the URL in an address bar or clicking on a link, icon, or the like, the browser may determine that the access request is an external request (relative to an internal request from a parent page); when the access request is initiated during the process of parsing the page data of the parent page, for example, the web system URL described above is included in an element such as an iframe tag or other element in the page data parsed into the parent page, the browser may determine that the access request is an internal request. Then the browser may add a flag in the access request, the first flag indicating that the access request is an external request and the second flag indicating that the access request is an internal request. Accordingly, after sending the marked access request to the server, the server may return the first page data or the second page data by parsing the mark in the access request to determine whether it is an external request or an internal request.
The tag added in the access request may include configuring the value of a specific field in the http header: the first flag is added when configured to the first value and the second flag is added when configured to the second value. Alternatively, the tag added in the access request may include whether a special field is added in the http header: this special field is not included, which corresponds to the addition of a first flag, and this special field is included, which corresponds to the addition of a second flag. Of course, the first mark or the second mark may be added by other means, which is not limited in this specification.
Fig. 8 is a schematic block diagram of an apparatus according to an exemplary embodiment. Referring to fig. 8, at the hardware level, the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile storage 810, although other applications may also include hardware as needed. The processor 802 reads a corresponding computer program from the nonvolatile memory 810 into the memory 808 and then runs, forming an access means of the network system on a logical level. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Referring to fig. 9, in a software implementation, the access device of the network system may include:
an acquisition unit 901 for acquiring page data of a new version network system;
and the loading unit 902 loads a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page.
Optionally, the parent page includes a plurality of function options, where the function options are used to adjust display content of the parent page; the child level page is nested and loaded in the parent level page when the selected functional option is associated with the legacy network system.
Optionally, the new version network system is the same as the URL of the old version network system; the apparatus further comprises:
a tagging unit 903 configured to tag an access request for the URL when the access request is detected, to indicate that the access request is an external request or an internal request originating from the parent page;
and a sending unit 904, configured to send the marked access request to a server, so that the server returns, for the external request, page data applied to load the parent page, or returns, for the internal request, page data applied to load the child page.
Optionally, the method further comprises:
a building unit 905 for building a route mapping table between the URL of the new version network system and the URL of the old version network system;
a monitoring unit 906, configured to monitor a message transferred between the parent page and the child page;
and an updating unit 907 for updating the URL of the message receiver according to the routing mapping table item when the monitored message content indicates that the URL of the message sender has changed the fragment identifier.
Optionally, the message is delivered by the message sender to the message receiver by invoking a PostMessage function.
Optionally, the network system is a single page application.
Optionally, the page data of the new version network system includes an iframe tag, where the iframe tag records a URL of the old version network system, so that the child level page is embedded in the parent level page.
Referring to fig. 10, in a software implementation, the access device of the network system may include:
an adding unit 1001, configured to add a flag in an access request for a network system URL, where the flag includes a first flag for indicating that an access target is a new version network system corresponding to the network system URL, or a second flag for indicating that an access target is an old version network system corresponding to the network system URL;
A sending unit 1002, configured to send the access request to a server, so that the server returns, according to the first flag, first page data for loading the new version network system, or returns, according to the second flag, second page data for loading the old version network system;
and the loading unit 1003 analyzes the first page data to load the page corresponding to the new version network system, or analyzes the second page data to load the page corresponding to the old version network system.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.
Claims (14)
1. A method for accessing a network system, comprising:
acquiring page data of a new version network system;
loading a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page;
the URL of the new version network system is the same as the URL of the old version network system; the method further comprises the steps of:
when an access request for the URL is detected, tagging the access request to indicate that the access request is an external request or an internal request originating from the parent page;
sending a marked access request to a server so that the server returns page data applied to loading the parent level page for the external request or returns page data applied to loading the child level page for the internal request;
And the page data of the new version network system contains an iframe tag, and the iframe tag records the URL of the old version network system so that the child page is embedded into the parent page.
2. The method of claim 1, wherein the parent page contains a number of function options for adjusting the display of the parent page; the child level page is nested and loaded in the parent level page when the selected functional option is associated with the legacy network system.
3. The method as recited in claim 1, further comprising:
establishing a route mapping table item between the URL of the new version network system and the URL of the old version network system;
monitoring messages transmitted between the parent page and the child page;
and updating the URL of the message receiver according to the routing mapping table item when the monitored message content indicates that the URL of the message sender is changed in the segment identifier.
4. A method according to claim 3, characterized in that the message is delivered by the message sender to the message receiver by invoking a PostMessage function.
5. The method of claim 1, wherein the network system is a single page application.
6. A method for accessing a network system, comprising:
adding a mark in an access request aiming at a network system URL, wherein the mark comprises a first mark used for indicating that an access target is a new version network system corresponding to the network system URL or a second mark used for indicating that the access target is an old version network system corresponding to the network system URL;
sending the access request to a server, and enabling the server to return first page data for loading the new version network system according to the first mark or return second page data for loading the old version network system according to the second mark;
analyzing the first page data to load the page corresponding to the new version network system, or analyzing the second page data to load the page corresponding to the old version network system;
the page data of the new version network system contains an iframe label, the iframe label records the URL of the old version network system, and the new version network system is identical with the URL of the old version network system.
7. An access device for a network system, comprising:
the acquisition unit acquires page data of the new version network system;
the loading unit is used for loading a parent page corresponding to the new version network system by analyzing the page data, wherein a child page corresponding to the old version network system is embedded in the parent page;
the URL of the new version network system is the same as the URL of the old version network system; the apparatus further comprises:
a tagging unit that tags an access request for the URL when the access request is detected to indicate that the access request is an external request or an internal request originating from the parent page;
a sending unit that sends a marked access request to a server, so that the server returns page data applied to loading the parent page for the external request or returns page data applied to loading the child page for the internal request;
and the page data of the new version network system contains an iframe tag, and the iframe tag records the URL of the old version network system so that the child page is embedded into the parent page.
8. The apparatus of claim 7, wherein the parent page contains a number of function options for adjusting the display of the parent page; the child level page is nested and loaded in the parent level page when the selected functional option is associated with the legacy network system.
9. The apparatus as recited in claim 7, further comprising:
the establishing unit is used for establishing a route mapping table item between the URL of the new version network system and the URL of the old version network system;
the monitoring unit monitors messages transmitted between the parent page and the child page;
and the updating unit is used for updating the URL of the message receiver according to the routing mapping table item when the monitored message content indicates that the URL of the message sender is changed in the segment identifier.
10. The apparatus of claim 9, wherein the message is delivered by a message sender to the message recipient by invoking a PostMessage function.
11. The apparatus of claim 7, wherein the network system is a single page application.
12. An access device for a network system, comprising:
An adding unit for adding a mark in an access request aiming at a network system URL, wherein the mark comprises a first mark used for indicating that an access target is a new version network system corresponding to the network system URL or a second mark used for indicating that the access target is an old version network system corresponding to the network system URL;
the sending unit sends the access request to a server, so that the server returns first page data for loading the new version network system according to the first mark or returns second page data for loading the old version network system according to the second mark;
the loading unit analyzes the first page data to load the page corresponding to the new version network system or analyzes the second page data to load the page corresponding to the old version network system;
the page data of the new version network system contains an iframe label, the iframe label records the URL of the old version network system, and the new version network system is identical with the URL of the old version network system.
13. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
Wherein the processor is configured to implement the method of any of claims 1-6 by executing the executable instructions.
14. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911096823.8A CN112783548B (en) | 2019-11-11 | 2019-11-11 | Access method and device of network system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911096823.8A CN112783548B (en) | 2019-11-11 | 2019-11-11 | Access method and device of network system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112783548A CN112783548A (en) | 2021-05-11 |
| CN112783548B true CN112783548B (en) | 2024-02-20 |
Family
ID=75749828
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911096823.8A Active CN112783548B (en) | 2019-11-11 | 2019-11-11 | Access method and device of network system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783548B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220396B (en) * | 2021-05-11 | 2024-04-16 | 北京达佳互联信息技术有限公司 | Embedded page management method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101082915A (en) * | 2006-05-29 | 2007-12-05 | 陈鹰 | Storage and update method of browsers local page |
| CN103577321A (en) * | 2012-08-07 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Multi-version parallel test method for web pages and server |
| CN103699600A (en) * | 2013-12-13 | 2014-04-02 | 北京奇虎科技有限公司 | Data processing method for web cache and browser |
| CN104714980A (en) * | 2013-12-17 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Page nesting path determination method and device |
| CN104978415A (en) * | 2015-06-26 | 2015-10-14 | 成都梦旅程网络科技有限公司 | Web page processing method convenient for quickly updating web pages |
| WO2017113060A1 (en) * | 2015-12-28 | 2017-07-06 | 华为技术有限公司 | Website access method and device, and website system |
| CN110287432A (en) * | 2019-06-28 | 2019-09-27 | 北京金山安全软件有限公司 | Network information processing method and device and electronic equipment |
| CN110399147A (en) * | 2019-06-04 | 2019-11-01 | 菜鸟智能物流控股有限公司 | Version release system and method and electronic equipment |
-
2019
- 2019-11-11 CN CN201911096823.8A patent/CN112783548B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101082915A (en) * | 2006-05-29 | 2007-12-05 | 陈鹰 | Storage and update method of browsers local page |
| CN103577321A (en) * | 2012-08-07 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Multi-version parallel test method for web pages and server |
| CN103699600A (en) * | 2013-12-13 | 2014-04-02 | 北京奇虎科技有限公司 | Data processing method for web cache and browser |
| CN104714980A (en) * | 2013-12-17 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Page nesting path determination method and device |
| CN104978415A (en) * | 2015-06-26 | 2015-10-14 | 成都梦旅程网络科技有限公司 | Web page processing method convenient for quickly updating web pages |
| WO2017113060A1 (en) * | 2015-12-28 | 2017-07-06 | 华为技术有限公司 | Website access method and device, and website system |
| CN110399147A (en) * | 2019-06-04 | 2019-11-01 | 菜鸟智能物流控股有限公司 | Version release system and method and electronic equipment |
| CN110287432A (en) * | 2019-06-28 | 2019-09-27 | 北京金山安全软件有限公司 | Network information processing method and device and electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| D. Hirashima ; M. Tanaka ; Y. Teshigawara.Development and evaluation of a minutes system focusing on importance in a meeting.《18th International Conference on Advanced Information Networking and Applications, 2004. AINA 2004》.2004,全文. * |
| 基于JSSh的动态网页获取研究与实现;万久士;李翔;林祥;;信息安全与通信保密(04);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112783548A (en) | 2021-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10733259B2 (en) | Web page access method and apparatus | |
| JP5075920B2 (en) | Web data usage platform | |
| US10180833B2 (en) | Cooperative web-assisted deep link redirection | |
| CN107250981B (en) | Dynamic loading of routes in single-page applications | |
| US9549035B2 (en) | Automatic updating of redirected location references | |
| US20090271690A1 (en) | Handling cross-domain web service calls | |
| US8627284B2 (en) | Managed system extensibility | |
| WO2016016734A1 (en) | Managing web browser cache for offline browsing | |
| US8655913B1 (en) | Method for locating web elements comprising of fuzzy matching on attributes and relative location/position of element | |
| US9781262B2 (en) | Methods and apparatus for voice-enabling a web application | |
| US20140040746A1 (en) | Methods and apparatus for voiced-enabling a web application | |
| US11262883B2 (en) | Associating browser with application | |
| US20100023953A1 (en) | Method and apparatus for executing application | |
| JP5004857B2 (en) | Application update information providing system and application update information providing method | |
| US9503551B2 (en) | Hybrid native networked applications | |
| US9292252B2 (en) | Methods and apparatus for voiced-enabling a web application | |
| CN111651703A (en) | Page jump method and device, electronic equipment and readable storage medium | |
| JP6779307B2 (en) | Method and device for page display | |
| CN112783548B (en) | Access method and device of network system | |
| US10846361B2 (en) | User-specific customization of web pages | |
| US10095791B2 (en) | Information search method and apparatus | |
| US20140344756A1 (en) | Information processing apparatus, and control method therefor | |
| CN103455543A (en) | Document management server, document management method, and storage medium | |
| US7970744B2 (en) | Minimizing problems in accessing referred content | |
| US9134930B2 (en) | Delayed content production |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |