CN113703760A - Page jump control method and device - Google Patents
Page jump control method and device Download PDFInfo
- Publication number
- CN113703760A CN113703760A CN202010440965.8A CN202010440965A CN113703760A CN 113703760 A CN113703760 A CN 113703760A CN 202010440965 A CN202010440965 A CN 202010440965A CN 113703760 A CN113703760 A CN 113703760A
- Authority
- CN
- China
- Prior art keywords
- page
- jump
- native
- current
- data structure
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000009191 jumping Effects 0.000 claims description 27
- 238000012545 processing Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 15
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a page jump control method and device, and relates to the technical field of computers. A specific implementation manner of the method comprises the steps of obtaining an identifier of a jump page, and searching whether a node comprising the identifier exists in a preset page data structure table; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table. Therefore, the method and the device for page jump can solve the problems that the existing page jump is low in efficiency and different types of page jumps are difficult to process.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a page jump control method and device.
Background
In the process that mobile terminal componentization is becoming a trend, more and more routing management schemes emerge, for example, a JLRouter (iOS-side routing component) which is relatively common in the market of the iOS side is similar to defining a certain protocol, and matching is performed according to a certain rule, so that corresponding jump is performed.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
however, with the current state of the art, although most of the business scenarios can be satisfied, the efficiency is extremely low. Meanwhile, in the cross-end page processing, for example, jumping between a read Native (open source cross-platform mobile application development framework, supporting iOS and Android) page and a Native page, it is not clear how to perform corresponding jumping. In addition, in the page jump process, how to perform corresponding jump back cannot be quickly realized, and if the jump back is a read Native page, how to find the read Native page and perform jump is not easy to process.
Disclosure of Invention
In view of this, embodiments of the present invention provide a page jump control method and apparatus, which can solve the problems that the existing page jump efficiency is low and different types of page jumps are not easy to process.
In order to achieve the above object, according to an aspect of the embodiments of the present invention, a page jump control method is provided, including obtaining an identifier of a jump page, so as to find whether a node including the identifier exists in a preset page data structure table; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
Optionally, the types of the current page and the jump page are identified, and the jump is executed based on the corresponding jump model, including:
and recognizing that the current page and the jump page are both native pages, extracting the information of the jump page in a page data structure table according to the jump page identification, and finding the information in the page stack of the current page for jumping.
Optionally, the types of the current page and the jump page are identified, and the jump is executed based on the corresponding jump model, including:
and recognizing that the current page and the jump page are both non-native pages, and jumping according to the jump page identification by utilizing a preset routing manager.
Optionally, after identifying that the current page and the jump page are both non-native pages, the method further includes:
extracting a native page identifier of a bearing jump page from a page data structure table according to the jump page identifier, and judging whether the native page identifier of the bearing jump page is consistent with the native page identifier of the bearing current page or not;
if so, skipping by utilizing a preset routing manager according to the skipping page identifier; and if not, acquiring the original page information of the bearing jump page, jumping based on the original page information of the bearing current page, and then jumping according to the jump page identifier by utilizing a preset routing manager.
Optionally, the types of the current page and the jump page are identified, and the jump is executed based on the corresponding jump model, including:
and identifying that the current page is a native page and the jump page is a non-native page, extracting information of the jump page in a page data structure table according to the jump page identification, further searching the information in a page stack of the current page to jump to the native page bearing the jump page, and then jumping according to the jump page identification by utilizing a preset routing manager.
Optionally, the types of the current page and the jump page are identified, and the jump is executed based on the corresponding jump model, including:
and identifying that the current page is a non-native page and the jump page is a native page, extracting information of the jump page in a page data structure table according to the jump page identification, and jumping to the jump page based on the native page information bearing the current page.
Optionally, the method further comprises:
and destroying the page corresponding to the node by removing the node in the page data structure table.
In addition, the invention also provides a page jump control device, which comprises an acquisition module, a page jump module and a page jump module, wherein the acquisition module is used for acquiring the identifier of a jump page; the processing module is used for searching whether a node comprising the identifier exists in a preset page data structure table; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
One embodiment of the above invention has the following advantages or benefits: the invention expands on the basis of page routing, maintains a data structure table, performs corresponding jump if the identification of the related page is found, and creates a new page if the identification of the related page is not found; meanwhile, the invention supports cross-end processing, so that the native page and the non-native page can be quickly searched and jumped.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of a main flow of a page jump control method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of page jump control according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of the main blocks of a page jump control apparatus according to an embodiment of the present invention;
FIG. 4 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 5 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a page jump control method according to an embodiment of the present invention, and as shown in fig. 1, the page jump control method includes:
and step S101, acquiring the identifier of the jump page.
In an embodiment, each page is provided with a pageId, i.e. identity. And each mark corresponds to the information of the page.
Step S102, searching whether a node comprising the identifier exists in a preset page data structure table, if so, performing step S103, otherwise, performing step S104.
In some embodiments, the invention sets a page data structure table in advance, the page data structure table is shared between a Native end and a non-Native end (for example, a read Native end) and is maintained at the Native end, and the data is added and deleted when the Native page and the non-Native end (for example, the read Native page) are generated and destroyed. Where native side refers to a logical implementation written in native technology code (e.g., OC/swift). Native pages refer to pages written in native technology code (e.g., OC/swift). A non-Native end (e.g., a read Native end) refers to a logic implementation that is written using non-Native technology code (e.g., read Native (JSX code)). A non-Native page (e.g., a read Native page) refers to a page written with non-Native technology code (e.g., using read Native (JSX code)).
It should be noted that, non-Native pages (e.g., the read Native page) will be finally converted into Native pages, for example, components of the read Native page will all have Native component correspondence, and JSX codes in the read Native code will all be converted back into Native codes during running to perform rendering and display.
As a specific embodiment, the native node indicates native page related information, the non-native node indicates non-native page related information, each page has a pageId, and corresponding page information is saved to the node, the saved information being different for the native page and the non-native page. Wherein, the native page may store the corresponding className: class name (mandatory), modeltype: jump type (optional). The non-native page needs to save the componentName: component name (mandatory), native pageid: the pageId of the native page that carries the non-native page (mandatory).
And S103, identifying the types of the current page and the jump page, and executing jump based on the corresponding jump model.
In some embodiments, if it is identified that the current page and the skipped page are both native pages, the information of the skipped page is extracted from the page data structure table according to the identifier of the skipped page, and the information is searched in the page stack of the current page for skipping.
In some embodiments, if the current page is identified as a native page and the skipped page is identified as a non-native page, the information of the skipped page is extracted from the page data structure table according to the identifier of the skipped page, and then the information is found in the page stack of the current page so as to skip to the native page carrying the skipped page, and then a preset routing manager is used for skipping according to the identifier of the skipped page.
In some embodiments, if the current page is identified as a non-native page and the jump page is identified as a native page, the information of the jump page is extracted from the page data structure table according to the jump page identifier, and then the jump page is jumped to based on the native page information bearing the current page.
It should be further noted that if it is identified that both the current page and the skipped page are non-native pages, the skipped page is skipped according to the skipped page identifier by using a preset routing manager.
Further, after recognizing that the current page and the jump page are both non-native pages, the native page identifier of the load jump page may be extracted from the page data structure table according to the jump page identifier, and it may be determined whether the native page identifier of the load jump page is consistent with the native page identifier of the load current page. If so, skipping by utilizing a preset routing manager according to the skipping page identifier; and if not, acquiring the original page information of the bearing jump page, jumping based on the original page information of the bearing current page, and then jumping according to the jump page identifier by utilizing a preset routing manager.
And step S104, creating a new page, and writing the new page information into the page data structure table.
In the embodiment, whether the pageId of the jump page exists is firstly searched in a maintained page data structure table, if so, corresponding jump is carried out according to the native page and the non-native page, if not, a new page is created, and related information is written into the page data structure table. That is to say, in the process of page jump in the application, as long as it is clear that the page is a native page or a non-native page, and finds the corresponding page pageId, the corresponding jump can be performed, and if the corresponding pageId is not found, a new page is created, and the information related to the page is added to the corresponding node. And searching the information of the native page bearing the non-native page through the pageId of the non-native page, and accordingly performing corresponding jump.
It is also worth noting that during page destruction, the page corresponding to the pageId may also be removed from the data structure.
In summary, the page jump control method of the present invention realizes that the global management page, that is, the corresponding jump can be performed regardless of the Native page or the non-Native page (for example, the read Native page). Moreover, if the jump is to an existing page, the jump can be quickly found and made. Meanwhile, the invention takes the page routing skip as a dimension, so that the page management flow of the mobile terminal is more uniform and ordered, and the invention has stronger operability and expansibility on the whole page in the application program.
Fig. 2 is a schematic diagram of page jumping according to another embodiment of the present invention, which is respectively illustrated for jumping between Native pages, between real Native (i.e. non-Native) pages, and between real Native pages and Native pages.
It should be noted that although the read Native page (referred to as RN page for short) is implemented by using the read Native technology, it essentially depends on a Native page, that is, a Native page is to be presented as a carrier, for example, the RN _ page1 page in fig. 2 is a read Native page, but depends on the Native _ page4 Native page container for presentation. Meanwhile, the page of the original end maintains a page stack of viewControllers, and corresponding routers are arranged among RN pages to maintain a page stack list.
Wherein, router is the route manager in the real Native technology. native _ page represents the native page, and RN _ page represents the RN page.
In a specific embodiment, if the single front page and the jump page are both native pages, i.e. flow 1 in fig. 2 points to, specifically:
in the process, a native _ page3 page jumps to a native _ page1 page, if a page id node of a native _ page1 page exists in a page data structure table, it is indicated that the jump is to an existing native page, information corresponding to the page id of the native _ page1 page is taken out from the page data structure table, and information corresponding to the page id is found in a page stack of the native _ page3 to perform corresponding jump, so that the jump of the native end is realized. All page information stacked before the native _ page3 page is included in the page stack.
And if the page Id node of the native _ page1 page is not found or does not exist in the page data structure table, creating a new native _ page1 page, and writing the page Id and page information of the page into the page data structure table.
In another specific embodiment, if both the single front page and the jump page are non-native pages (RN pages), i.e. the direction of flows 2-1 and 2-2 in fig. 2, specifically:
the RN page jump is divided into two cases, the first is to jump the RN page in the present context (context means context, i.e. context run by real Native) as in the flow 2-1 in fig. 2, and the second is to jump in a different context (i.e. context) as in the flow 2-2 in fig. 2.
In the process 2-1, in the context of the same real Native, if the page id of the rn _ page1 page exists in the page data structure table, the Native page id information of the page id and the Native page id information of the rn _ page3 are compared to each other (i.e., whether the comparison is in the same context). And if the two nodes are the same, performing corresponding jump by using the router at the RN end. If not, a new rn _ page1 page is created and the new page's information is written to the page data structure table.
In the process 2-2, jumping is performed for contexts (i.e., contexts) of different real Native, if there is a page id of RN _ page1 in the page data structure table, the jumping is performed for an RN page that already exists and is not in the same context, and the Native page id information of the page id and the Native page id information of the current RN _ page4 are first compared (i.e., whether the Native page ids are the same or not is compared). Because the native page Ids are different at different contexts (the native page Id of rn _ page4 is native _ page7, and the native page Id of rn _ page1 is native _ page4), the native interface native _ page4 bearing rn _ page1 is found, and the native end is jumped on the basis of the native page of the dependent native _ page 7. If the page Id of RN _ page1 does not exist in the page data structure table, a RN page is newly created, and corresponding information is written into the page data structure table.
In yet another specific embodiment, if the native page jumps to the RN page: i.e. the direction of flow 3 in fig. 2, specifically includes:
the process includes that native _ page5 jumps to an RN _ page2 page, whether a page Id of RN _ page2 exists is searched in a page data structure table, if yes, relevant information corresponding to the page Id is taken out, and the RN _ page2 depends on a native interface of the native _ page4, so that the page needs to jump to a native _ page4 page first, and then a router of an RN end is used for carrying out relevant jumping according to the page Id. If the page Id does not exist, a new rn _ page2 page is created and the information for the new page is written to the page data structure table.
In yet another specific embodiment, if the RN page jumps to the native page: i.e. the direction of flow 4 in fig. 2, specifically includes:
the process is that RN _ page4 jumps to native _ page5, whether a page id of native _ page5 exists is searched in a page data structure table, if yes, the original end jump is carried out according to the related information of the page id, because RN _ page4 depends on a native _ page7 page, and the jump from the RN page to the original page is similar to the jump between the native pages. If the page Id of native _ page5 does not exist in the page data structure table, a new page is created and the corresponding information is written into the page data structure table.
It can be seen that the present invention expands on the basis of page routing, maintains a data structure table, performs corresponding jump if the pageId of the relevant page is found, and creates a new page if the pageId of the relevant page is not found, and simultaneously supports cross-end processing, so that Native and non-Native pages (such as read Native, Flutter cross-end technology, etc.) can also be quickly searched and jumped.
Wherein, Flutter is the mobile UI framework of google, and can quickly construct a high-quality native user interface on iOS and Android.
Fig. 3 is a schematic diagram of main blocks of a page jump control apparatus according to an embodiment of the present invention, and as shown in fig. 3, the page jump control apparatus 300 includes an obtaining module 301 and a processing module 302. The obtaining module 301 obtains an identifier of a jump page; the processing module 302 searches whether a node including the identifier exists in a preset page data structure table; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
In some embodiments, the processing module 302 identifies the current page and the category of the jump page, and performs the jump based on the corresponding jump model, including:
and recognizing that the current page and the jump page are both native pages, extracting the information of the jump page in a page data structure table according to the jump page identification, and finding the information in the page stack of the current page for jumping.
In some embodiments, the processing module 302 identifies the current page and the category of the jump page, and performs the jump based on the corresponding jump model, including:
and recognizing that the current page and the jump page are both non-native pages, and jumping according to the jump page identification by utilizing a preset routing manager.
In some embodiments, after the processing module 302 identifies that the current page and the jumped page are both non-native pages, further comprising:
extracting a native page identifier of a bearing jump page from a page data structure table according to the jump page identifier, and judging whether the native page identifier of the bearing jump page is consistent with the native page identifier of the bearing current page or not;
if so, skipping by utilizing a preset routing manager according to the skipping page identifier; and if not, acquiring the original page information of the bearing jump page, jumping based on the original page information of the bearing current page, and then jumping according to the jump page identifier by utilizing a preset routing manager.
In some embodiments, the processing module 302 identifies the current page and the category of the jump page, and performs the jump based on the corresponding jump model, including:
and identifying that the current page is a native page and the jump page is a non-native page, extracting information of the jump page in a page data structure table according to the jump page identification, further searching the information in a page stack of the current page to jump to the native page bearing the jump page, and then jumping according to the jump page identification by utilizing a preset routing manager.
In some embodiments, the processing module 302 identifies the current page and the category of the jump page, and performs the jump based on the corresponding jump model, including:
and identifying that the current page is a non-native page and the jump page is a native page, extracting information of the jump page in a page data structure table according to the jump page identification, and jumping to the jump page based on the native page information bearing the current page.
In some embodiments, the processing module 302 is further configured to destroy the page corresponding to the node by removing the node in the page data structure table.
It should be noted that the page jump control method and the page jump control device of the present invention have a corresponding relationship in the specific implementation content, so the repeated content is not described again.
Fig. 4 illustrates an exemplary system architecture 400 of a page jump control method or apparatus, a page jump control discrimination or discrimination apparatus, to which embodiments of the present invention may be applied.
As shown in fig. 4, the system architecture 400 may include terminal devices 401, 402, 403, a network 404, and a server 405. The network 404 serves as a medium for providing communication links between the terminal devices 401, 402, 403 and the server 405. Network 404 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use terminal devices 401, 402, 403 to interact with a server 405 over a network 404 to receive or send messages or the like. The terminal devices 401, 402, 403 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 401, 402, 403 may be various electronic devices having a page jump control screen or a page jump control discrimination screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 405 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 401, 402, 403. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the page jump control method or the page jump control determination method provided in the embodiment of the present invention is generally executed by the server 405, and accordingly, the computing device is generally disposed in the server 405.
It should be understood that the number of terminal devices, networks, and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM503, various programs and data necessary for the operation of the computer system 500 are also stored. The CPU501, ROM502, and RAM503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output section 507 including a display such as a Cathode Ray Tube (CRT), a liquid crystal page jump controller (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 501.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an acquisition module and a processing module. Wherein the names of the modules do not in some cases constitute a limitation of the module itself.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include obtaining an identifier of a jump page to look up in a preset page data structure table whether a node including the identifier exists; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
According to the technical scheme of the embodiment of the invention, the problems that the existing page jump efficiency is low and different types of page jumps are difficult to process can be solved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A page jump control method is characterized by comprising the following steps:
acquiring an identifier of a jump page to find out whether a node comprising the identifier exists in a preset page data structure table;
if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
2. The method of claim 1, wherein the categories of the current page and the jump page are identified, and the jump is performed based on a corresponding jump model, comprising:
and recognizing that the current page and the jump page are both native pages, extracting the information of the jump page in a page data structure table according to the jump page identification, and finding the information in the page stack of the current page for jumping.
3. The method of claim 1, wherein the categories of the current page and the jump page are identified, and the jump is performed based on a corresponding jump model, comprising:
and recognizing that the current page and the jump page are both non-native pages, and jumping according to the jump page identification by utilizing a preset routing manager.
4. The method of claim 3, wherein after identifying that the current page and the jumped page are both non-native pages, further comprising:
extracting a native page identifier of a bearing jump page from a page data structure table according to the jump page identifier, and judging whether the native page identifier of the bearing jump page is consistent with the native page identifier of the bearing current page or not;
if so, skipping by utilizing a preset routing manager according to the skipping page identifier; and if not, acquiring the original page information of the bearing jump page, jumping based on the original page information of the bearing current page, and then jumping according to the jump page identifier by utilizing a preset routing manager.
5. The method of claim 1, wherein the categories of the current page and the jump page are identified, and the jump is performed based on a corresponding jump model, comprising:
and identifying that the current page is a native page and the jump page is a non-native page, extracting information of the jump page in a page data structure table according to the jump page identification, further searching the information in a page stack of the current page to jump to the native page bearing the jump page, and then jumping according to the jump page identification by utilizing a preset routing manager.
6. The method of claim 1, wherein the categories of the current page and the jump page are identified, and the jump is performed based on a corresponding jump model, comprising:
and identifying that the current page is a non-native page and the jump page is a native page, extracting information of the jump page in a page data structure table according to the jump page identification, and jumping to the jump page based on the native page information bearing the current page.
7. The method according to any one of claims 1-6, further comprising:
and destroying the page corresponding to the node by removing the node in the page data structure table.
8. A page jump control apparatus, comprising:
the acquisition module is used for acquiring the identifier of the jump page;
the processing module is used for searching whether a node comprising the identifier exists in a preset page data structure table; if so, identifying the types of the current page and the jump page, and executing jump based on a corresponding jump model; if not, creating a new page, and further writing the information of the new page into the page data structure table.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010440965.8A CN113703760A (en) | 2020-05-22 | 2020-05-22 | Page jump control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010440965.8A CN113703760A (en) | 2020-05-22 | 2020-05-22 | Page jump control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113703760A true CN113703760A (en) | 2021-11-26 |
Family
ID=78646198
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010440965.8A Pending CN113703760A (en) | 2020-05-22 | 2020-05-22 | Page jump control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113703760A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160182650A1 (en) * | 2014-12-22 | 2016-06-23 | Guangzhou Ucweb Computer Technology Co., Ltd. | Method and apparatus for isolating page cookie |
| WO2016146056A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Page switching method and device |
| CN106815276A (en) * | 2015-11-27 | 2017-06-09 | 阿里巴巴集团控股有限公司 | Method for page jump and device |
| CN108255550A (en) * | 2017-11-27 | 2018-07-06 | 深圳市小牛在线互联网信息咨询有限公司 | Method for page jump, device, storage medium and computer equipment |
| CN109634604A (en) * | 2018-11-30 | 2019-04-16 | 南京天溯自动化控制系统有限公司 | IOS method for page jump and its system based on mixed developing |
| CN109740090A (en) * | 2018-12-25 | 2019-05-10 | 南京天溯自动化控制系统有限公司 | A kind of android page return jump method and its system based on mixed developing |
-
2020
- 2020-05-22 CN CN202010440965.8A patent/CN113703760A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160182650A1 (en) * | 2014-12-22 | 2016-06-23 | Guangzhou Ucweb Computer Technology Co., Ltd. | Method and apparatus for isolating page cookie |
| WO2016146056A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Page switching method and device |
| CN106815276A (en) * | 2015-11-27 | 2017-06-09 | 阿里巴巴集团控股有限公司 | Method for page jump and device |
| CN108255550A (en) * | 2017-11-27 | 2018-07-06 | 深圳市小牛在线互联网信息咨询有限公司 | Method for page jump, device, storage medium and computer equipment |
| CN109634604A (en) * | 2018-11-30 | 2019-04-16 | 南京天溯自动化控制系统有限公司 | IOS method for page jump and its system based on mixed developing |
| CN109740090A (en) * | 2018-12-25 | 2019-05-10 | 南京天溯自动化控制系统有限公司 | A kind of android page return jump method and its system based on mixed developing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109683998B (en) | Internationalization realization method, device and system | |
| US11563674B2 (en) | Content based routing method and apparatus | |
| CN107844324B (en) | Client page jump processing method and device | |
| CN107302597B (en) | Message file pushing method and device | |
| CN107480205B (en) | Method and device for partitioning data | |
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| CN112835904A (en) | Data processing method and data processing device | |
| CN112988583A (en) | Method and device for testing syntax compatibility of database | |
| CN110705271A (en) | System and method for providing natural language processing service | |
| CN113271307B (en) | Data assembling method, device, computer system and storage medium | |
| CN110647327B (en) | Method and device for dynamic control of user interface based on card | |
| US20130151945A1 (en) | Processing Published and Subscribed Events | |
| CN110266596B (en) | Message processing method, device, equipment and computer readable storage medium | |
| CN112948138A (en) | Method and device for processing message | |
| CN113722007B (en) | Configuration method, device and system of VPN branch equipment | |
| CN115495740A (en) | Virus detection method and device | |
| CN113703760A (en) | Page jump control method and device | |
| CN114896244A (en) | Method, device and equipment for configuring database table and computer readable medium | |
| CN113656041A (en) | Data processing method, device, equipment and storage medium | |
| CN113742485A (en) | Method and device for processing text | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN110796137A (en) | Method and device for identifying image | |
| CN112600918B (en) | Industrial control edge big data efficient processing method and system based on BS architecture | |
| CN113127416A (en) | Data query method and device | |
| CN112835609A (en) | Method and device for modifying dependent package download address |
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 |