CN110851688A - Page request method, device and equipment - Google Patents
Page request method, device and equipment Download PDFInfo
- Publication number
- CN110851688A CN110851688A CN201911096162.9A CN201911096162A CN110851688A CN 110851688 A CN110851688 A CN 110851688A CN 201911096162 A CN201911096162 A CN 201911096162A CN 110851688 A CN110851688 A CN 110851688A
- Authority
- CN
- China
- Prior art keywords
- user
- target page
- page
- information
- request
- 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
Images
Classifications
-
- 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/953—Querying, e.g. by the use of web search engines
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a page request method, a device and equipment, wherein the method comprises the following steps: receiving an operation instruction of a user; determining a target page corresponding to the operation instruction; judging whether the information of the target page exists in the historical page request record of the user or not; if the information of the target page exists in the historical page request record, generating the target page according to the information of the target page and a first preset rendering condition; and if the information of the target page does not exist in the historical page request record, requesting the target page from a server corresponding to the target page. The method and the device for requesting the target page to be accessed by the user according to the operation instruction of the user are realized.
Description
Technical Field
The present application relates to the field of information technology, and in particular, to a page request method, apparatus, and device.
Background
Customer Relationship Management (CRM) system is a tool for coordinating the interaction between enterprise and Customer in sales, marketing and service and providing personalized interaction and service to Customer by using information technology and Internet technology.
Different enterprises can develop CRM applications according to own needs, and when the conventional CRM applications are used for page access, page requests are required to be sent to corresponding servers aiming at each page access, and corresponding page information is returned through the servers to generate corresponding access pages. This page request approach often causes a page stuck phenomenon.
Disclosure of Invention
An object of the embodiments of the present application is to provide a page request method, device and apparatus, which are used to request a target page to be accessed by a user according to an operation instruction of the user.
A first aspect of an embodiment of the present application provides a page request method, including: receiving an operation instruction of a user; determining a target page corresponding to the operation instruction; judging whether the information of the target page exists in the historical page request record of the user or not; if the information of the target page exists in the historical page request record, generating the target page according to the information of the target page and a first preset rendering condition; and if the information of the target page does not exist in the historical page request record, requesting the target page from a server corresponding to the target page.
In an embodiment, before the receiving the operation instruction of the user, the method includes: acquiring login information of the user; judging whether the user is a current effective user or not according to the login information; if the user is the current effective user, acquiring basic information of the user; the basic information includes: the identity information of the user, the historical page request record and the page access authority of the user; and generating an operation page according to the basic information, wherein the operation page is used for receiving the operation instruction of the user.
In an embodiment, the requesting the target page from the server corresponding to the target page includes: generating request information of the target page according to the operation instruction; and sending the request information to the server so as to provide response data returned by the server according to the request information.
In an embodiment, after the sending the request message to the server, the method further includes: receiving the response data of the server; judging whether the response data contains the response of the target page or not; if the response data comprises the response of the target page, generating the target page according to the response of the target page and a second preset rendering condition, and displaying the target page; and if the response data does not contain the response of the target page, sending a prompt.
In an embodiment, the preset rendering condition includes: a page theme style and/or a data presentation style.
A second aspect of the embodiments of the present application provides a page request apparatus, including: the receiving module is used for receiving an operation instruction of a user; the determining module is used for determining a target page corresponding to the operation instruction; the first judgment module is used for judging whether the information of the target page exists in the historical page request record of the user; the first generation module is used for generating the target page according to the information of the target page and a first preset rendering condition if the information of the target page exists in the historical page request record; and the request module is used for requesting the target page from a server corresponding to the target page if the information of the target page does not exist in the historical page request record.
In one embodiment, the method further comprises: the first acquisition module is used for acquiring the login information of the user before the operation instruction of the user is received; the second judgment module is used for judging whether the user is a current effective user or not according to the login information; the second acquisition module is used for acquiring the basic information of the user if the user is the current effective user; the basic information includes: the identity information of the user, the historical page request record and the page access authority of the user; and the second generation module is used for generating an operation page according to the basic information, and the operation page is used for receiving the operation instruction of the user.
In an embodiment, the requesting the target page from the server corresponding to the target page includes: generating request information of the target page according to the operation instruction; and sending the request information to the server so as to provide response data returned by the server according to the request information.
In an embodiment, after the sending the request message to the server, the method further includes: receiving the response data of the server; judging whether the response data contains the response of the target page or not; if the response data comprises the response of the target page, generating the target page according to the response of the target page and a second preset rendering condition, and displaying the target page; and if the response data does not contain the response of the target page, sending a prompt.
A third aspect of embodiments of the present application provides an electronic device, including: a memory to store a computer program; the processor is configured to execute the method according to the first aspect and any embodiment of the present application, so as to request a target page to be accessed by a user according to an operation instruction of the user.
According to the page request method, the page request device and the page request equipment, firstly, a target page which a user wants to access is determined according to an operation instruction of the user, then, whether information of the target page exists or not is inquired in a historical page request record of the user, if the information indicates that the user accesses the target page, the information of the target page in the historical record and a first preset rendering condition are directly used for generating the target page. And if not, the target page is required to be requested to a server corresponding to the target page, so that the target page to be accessed by the user is requested according to the operation instruction of the user.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a page request application scenario according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating a page request method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a page request method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a page request device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the present application, the terms "first," "second," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
As shown in fig. 1, the present embodiment provides an electronic device 100, including: at least one processor 11 and a memory 12, one processor being exemplified in fig. 1. The processor 11 and the memory 12 are connected by a bus 10, and the memory 12 stores instructions executable by the processor 11, the instructions being executed by the processor 11 to request a target page to be accessed by a user according to an operation instruction of the user.
Please refer to fig. 2, which is a page request application scenario 200 according to an embodiment of the present application, including: a terminal 210 and at least one server 230, wherein the main functions of the respective parts are as follows:
the CRM application 222 is installed in the terminal 210, and the terminal 210 further includes a user interface 211 and a login platform 220, where the user interface 211 may be a touch screen of a mobile phone. The user can input an operation instruction through the user interface 211.
The CRM application 222 typically contains ACMCRM (national thread) products and MCRM (mobile CRM) products, which can share the same background between them. The page of the front-end acm product can be implemented by using a lightweight front-end framework vue.js, and the front-end User Interface 211(User Interface, abbreviated as "UI") framework can use a VUX framework, which is a mobile-end UI component library based on weii and vue.js. Js is a progressive framework for building data-driven web interfaces. Js is to realize the data binding of response and combined view components through an application program interface as simple as possible, so that the page response speed can be improved from the original 5 seconds to 2 seconds. Js is generally used for development of the mobile end, whereas angularJS is generally used for large projects, and the MCRM product can be implemented using angularJS. The internal logic relation is connected among the systems through jumping, and the PC end cable detail report can be communicated with the ACMCRM product of the mobile end for use.
The login platform 220 may be an office platform of an enterprise, and a user with CRM authority may directly enter a home page of CRM through the login platform 220, so the CRM application 222 may be associated with the login platform 220, and further, login information of the user is obtained through the login platform 220. The terminal 210 can be connected to the servers 230 via the internet, and each server 230 can store page information associated with the CRM application 222, such as web page data, and when a user accesses a target page of the CRM application 222, the user can request the information of the target page from the server 230.
When the data of the mobile end MCRM product is communicated with the data of the PC end, for the condition of large data volume, when the ACMCRM processes the imported data of the PC end line detail report, the data can be processed by using a batch submission method, and the ACMCRM can also be matched with a timer, for example, the imported data can be processed every 2 hours, so that the situation of blocking during business operation is effectively prevented, on one hand, the response time of multi-party verification of the PC end is solved, on the other hand, the response speed of a system is improved by multi-thread, and the import of the system data is improved from 100 pieces/piece in the previous period to 5000 pieces/piece.
Please refer to fig. 3, which is a page request method according to an embodiment of the present application, which can be executed by the electronic device 100 shown in fig. 1. The method can also be applied to the page request application scenario 200 shown in fig. 2, and is executed by the terminal 210 in fig. 2 to implement requesting a target page to be accessed by a user according to an operation instruction of the user. The method comprises the following steps:
step 301: and receiving an operation instruction of a user.
In this step, the CRM application 222 is installed in the terminal 210, and the user can input an operation instruction through the user interface 211 of the terminal 210, where the operation instruction is an operation instruction corresponding to a target page of the CRM application 222 that needs to be accessed.
Step 302: and determining a target page corresponding to the operation instruction.
In this step, after receiving the user operation instruction, the terminal 210 determines the target page corresponding to the operation instruction, for example, the user clicks the identifier of the target page through the user interface 211, and the terminal 210 receives the click instruction and determines the target page according to the identifier associated with the click instruction.
Step 303: and judging whether the historical page request records of the user have the information of the target page. If so, step 304 is entered, otherwise step 305 is entered.
In this step, when a user accesses a CRM page each time, the access data of the user can be generated into a history page request record, wherein the history page request record contains data of the access history page of the user and is stored locally, when the user wants to access a target page, whether the history page request record of the user has information of the target page is firstly judged, and a loading mode of the target page is determined according to a judgment result.
Step 304: and generating the target page according to the information of the target page and the first preset rendering condition.
In this step, if the history page request record includes information of the target page, which indicates that the user has visited the target page once and the information of the target page is locally stored, the information of the target page may be directly loaded from the local storage, the package data of the target page may be generated according to the first preset rendering condition, the service logic of the page display may be updated according to the package data, and the remaining user interfaces 211 may be bound, so that the target page may be displayed on the user interface 211 for the user to view. In an embodiment, the first preset rendering condition may include: page subject style and/or data presentation style, such as clue list style in CRM. Namely, the packaging data of the target page is rendered according to the preset page theme style or the data display style.
Step 305: the target page is requested from the server 230 corresponding to the target page.
In this step, if the history page request record does not include the information of the target page, which indicates that the user does not locally store the information of the target page, or the user accesses the target page for the first time, the user requests the corresponding server 230 for the target page to be accessed by the user.
The page request method comprises the steps of firstly determining a target page which a user wants to access according to an operation instruction of the user, then inquiring in a historical page request record of the user to see whether information of the target page exists or not, and if the information indicates that the user accesses the target page, directly generating the target page by the information of the target page in the historical record and a first preset rendering condition. If not, the target page needs to be requested to the server 230 corresponding to the target page, so that the target page to be accessed by the user is requested according to the operation instruction of the user.
Please refer to fig. 4, which is a page request method according to an embodiment of the present application, which can be executed by the electronic device 100 shown in fig. 1. The method can also be applied to the page request application scenario 200 shown in fig. 2, and is executed by the terminal 210 in fig. 2 to implement requesting a target page to be accessed by a user according to an operation instruction of the user. The method comprises the following steps:
step 401: and acquiring login information of the user.
In this step, for the CRM application 222 of the enterprise, the user can log in to the office platform of the enterprise through the login platform 220 first, the user with CRM authority can directly download and install the CRM module, the user can directly enter the home page of the CRM through the login platform 220, the CRM application 222 can be associated with the login platform 220, and then the login information of the user is obtained through the login platform 220.
Step 402: and judging whether the user is the current effective user or not according to the login information. If so, step 403 is entered, otherwise the page request module 505 of the CRM application 222 is not displayed and the user's login information may continue to be retrieved.
In this step, the login information at least includes the login ID and the login status of the user, such as cookie and session, and it can be determined whether the user is a currently valid user through the login information. In practical applications, if the user a enters the CRM application 222 through the office platform, when the terminal 210 acquires the login information of the user a, it needs to determine whether the user a currently logs in the office platform or not, and if so, it indicates that the user a is a currently valid user, then step 403 is performed. If the current user B is logged in the office platform, the user A is not the current valid user. The page request module 505 of the CRM application 222 is not displayed. In the process, the user can modify the login information, the judgment time can be preset, for example, 30 seconds can be preset, and if the login information of the user A is judged to be not the current valid user in 30 seconds, a prompt can be sent.
Step 403: and acquiring basic information of the user. The basic information includes: identity information of the user, historical page request records, and page access permissions of the user.
In this step, the basic information of the user at least includes: identity information of the user, historical page request records, and page access permissions of the user. The identity information of the user can be the name, the job number, the post, the affiliated department and the like of the user, the historical page request record can be historical record data logged in by the user, and the page access authority can be the access authority of a related menu bar of the CRM and the like. If the user is the current effective user, the local storage can be firstly inquired, if the local storage has the basic information of the user, the basic information is directly acquired from the local storage, and if the local storage does not have the basic information or is incomplete, the lacking basic information is prompted to the user, and the basic information can be acquired through user input.
Step 404: and generating an operation page according to the basic information, wherein the operation page is used for receiving an operation instruction of a user.
In this step, the page access authority in the basic information may be the access authority of the related menu bar of the CRM, and then the related menu bar of the CRM to which the user has the access authority may be displayed on the operation page, so that the user operates the related menu bar on the operation page.
Step 405: and receiving an operation instruction of a user. See the description of step 301 in the above embodiments for details.
Step 406: and determining a target page corresponding to the operation instruction. See the description of step 302 in the above embodiments for details.
Step 407: and judging whether the historical page request records of the user have the information of the target page. If so, step 408 is entered, otherwise step 409 is entered. See the description of step 303 in the above embodiments for details.
Step 408: and generating the target page according to the information of the target page and the first preset rendering condition. See the description of step 304 in the above embodiments for details.
Step 409: and generating request information of the target page according to the operation instruction.
In this step, if the history page request record does not contain the information of the target page, which indicates that the user does not locally store the information of the target page, or the user accesses the target page for the first time, first, request information of the target page is generated, where the request information may be axios request data.
Step 410: the request information is sent to the server 230 for the server 230 to return response data according to the request information.
In this step, axios request data of the target page generated in step 409 is sent to the corresponding server 230, so that the server 230 returns response data according to the request information.
Step 411: response data of the server 230 is received.
In this step, each target page accessed by the user may correspond to a different server 230, and when the corresponding server 230 receives axios request data, response data is returned, and the response data returned by the server 230 is received in real time. Certainly, a timeout reminder may be set, and if the returned response data of the server 230 is not received within preset 3 seconds, the user is prompted to process the response data in time.
Step 412: and judging whether the response data contains the response of the target page. If so, step 413 is entered, otherwise, step 414 is entered.
Step 413: and generating a target page according to the response of the target page and the second preset rendering condition, and displaying the target page.
In this step, if the response data includes a response of the target page, which indicates that the server 230 successfully returns the information of the target page, the packaged data of the target page may be generated according to the response data and the second preset rendering condition, the service logic displayed by the page is updated according to the packaged data, and the rest of the user interfaces 211 are bound, so that the target page may be displayed on the user interface 211 for the user to view. In an embodiment, the second predetermined rendering condition may include: page subject style and/or data presentation style, such as clue list style in CRM. Namely, the packaging data of the target page is rendered according to the preset page theme style or the data display style.
Step 414: and if the response data does not contain the response of the target page, sending out a prompt.
In this step, if the server 230 returns the response data, but the response data does not have the information of the target page, which indicates that a failure may occur in the server 230 when the information of the target page is returned, a prompt may be sent to the user for the user to handle in time.
Please refer to fig. 5, which is a diagram illustrating a page request apparatus 500 according to an embodiment of the present application, which can be applied to the electronic device 100 shown in fig. 1. The apparatus can also be applied to the page request application scenario 200 shown in fig. 2, that is, to the terminal 210 in fig. 2, to implement a target page requested to be accessed by a user according to an operation instruction of the user. The device includes: the system comprises a receiving module 501, a determining module 502, a first judging module 503, a first generating module 504 and a requesting module 505, wherein the principle relationship of each module is as follows:
the receiving module 501 is configured to receive an operation instruction of a user. See the description of step 301 in the above embodiment for details.
The determining module 502 is configured to determine a target page corresponding to the operation instruction. See the description of step 302 in the above embodiment for details.
The first determining module 503 is configured to determine whether information of a target page exists in a history page request record of a user. See the description of step 303 in the above embodiment for details.
The first generating module 504 is configured to generate the target page according to the information of the target page and a first preset rendering condition if the information of the target page exists in the historical page request record. See the description of step 304 in the above embodiment for details.
The request module 505 is configured to request the server 230 corresponding to the target page for the target page if the history page request record does not include the information of the target page. For details, refer to the description of step 305 in the above embodiment.
In one embodiment, the method further comprises:
the first obtaining module 506 is configured to obtain login information of the user before receiving an operation instruction of the user. For details, refer to the description of step 401 in the above embodiment.
And a second judging module 507, configured to judge whether the user is a currently valid user according to the login information. See the description of step 402 in the above embodiment for details.
A second obtaining module 508, configured to obtain basic information of the user if the user is a current valid user. The basic information includes: identity information of the user, historical page request records, and page access permissions of the user. See the description of step 403 in the above embodiment for details.
A second generating module 509, configured to generate an operation page according to the basic information, where the operation page is used to receive an operation instruction of a user. See the description of step 404 in the above embodiment for details.
In one embodiment, requesting the target page from the server 230 corresponding to the target page includes: and generating request information of the target page according to the operation instruction. The request information is sent to the server 230 for the server 230 to return response data according to the request information. For details, refer to the descriptions of step 409 to step 410 in the above embodiments.
In one embodiment, after sending the request message to the server 230, the method further includes: response data of the server 230 is received. And judging whether the response data contains the response of the target page. And if the response data contains the response of the target page, generating the target page according to the response of the target page and the second preset rendering condition, and displaying the target page. And if the response data does not contain the response of the target page, sending out a prompt. For details, refer to the descriptions of step 411 to step 414 in the above embodiments.
An embodiment of the present invention further provides a storage medium readable by an electronic device, including: a program that, when run on an electronic device, causes the electronic device to perform all or part of the procedures of the methods in the above-described embodiments. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid-State Drive (SSD), or the like. The storage medium may also comprise a combination of memories of the kind described above.
Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A page request method, comprising:
receiving an operation instruction of a user;
determining a target page corresponding to the operation instruction;
judging whether the information of the target page exists in the historical page request record of the user or not;
if the information of the target page exists in the historical page request record, generating the target page according to the information of the target page and a first preset rendering condition;
and if the information of the target page does not exist in the historical page request record, requesting the target page from a server corresponding to the target page.
2. The method according to claim 1, before the receiving of the operation instruction of the user, comprising:
acquiring login information of the user;
judging whether the user is a current effective user or not according to the login information;
if the user is the current effective user, acquiring basic information of the user; the basic information includes: the identity information of the user, the historical page request record and the page access authority of the user;
and generating an operation page according to the basic information, wherein the operation page is used for receiving the operation instruction of the user.
3. The method of claim 1, wherein requesting the target page from the server corresponding to the target page comprises:
generating request information of the target page according to the operation instruction;
and sending the request information to the server so as to provide response data returned by the server according to the request information.
4. The method of claim 3, further comprising, after said sending the request message to the server:
receiving the response data of the server;
judging whether the response data contains the response of the target page or not;
if the response data comprises the response of the target page, generating the target page according to the response of the target page and a second preset rendering condition, and displaying the target page;
and if the response data does not contain the response of the target page, sending a prompt.
5. The method of claim 1, wherein the preset rendering condition comprises: a page theme style and/or a data presentation style.
6. A page request apparatus, comprising:
the receiving module is used for receiving an operation instruction of a user;
the determining module is used for determining a target page corresponding to the operation instruction;
the first judgment module is used for judging whether the information of the target page exists in the historical page request record of the user;
the first generation module is used for generating the target page according to the information of the target page and a first preset rendering condition if the information of the target page exists in the historical page request record;
and the request module is used for requesting the target page from a server corresponding to the target page if the information of the target page does not exist in the historical page request record.
7. The apparatus of claim 6, further comprising:
the first acquisition module is used for acquiring the login information of the user before the operation instruction of the user is received;
the second judgment module is used for judging whether the user is a current effective user or not according to the login information;
the second acquisition module is used for acquiring the basic information of the user if the user is the current effective user; the basic information includes: the identity information of the user, the historical page request record and the page access authority of the user;
and the second generation module is used for generating an operation page according to the basic information, and the operation page is used for receiving the operation instruction of the user.
8. The apparatus of claim 6, wherein the requesting the target page from the server corresponding to the target page comprises:
generating request information of the target page according to the operation instruction;
and sending the request information to the server so as to provide response data returned by the server according to the request information.
9. The apparatus of claim 8, further comprising, after the sending the request message to the server:
receiving the response data of the server;
judging whether the response data contains the response of the target page or not;
if the response data comprises the response of the target page, generating the target page according to the response of the target page and a second preset rendering condition, and displaying the target page;
and if the response data does not contain the response of the target page, sending a prompt.
10. An electronic device, comprising:
a memory to store a computer program;
a processor configured to execute the method according to any one of claims 1 to 5 to request a target page to be accessed by a user according to an operation instruction of the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911096162.9A CN110851688A (en) | 2019-11-11 | 2019-11-11 | Page request method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911096162.9A CN110851688A (en) | 2019-11-11 | 2019-11-11 | Page request method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110851688A true CN110851688A (en) | 2020-02-28 |
Family
ID=69601098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911096162.9A Pending CN110851688A (en) | 2019-11-11 | 2019-11-11 | Page request method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851688A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112732136A (en) * | 2020-12-30 | 2021-04-30 | 五八有限公司 | Desktop component adding method, desktop component adding device and terminal equipment |
| CN114443196A (en) * | 2022-01-17 | 2022-05-06 | 苏州浪潮智能科技有限公司 | User interface processing method and system and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120047445A1 (en) * | 2010-08-20 | 2012-02-23 | Salesforce.Com, Inc. | Pre-fetching pages and records in an on-demand services environment |
| CN106354879A (en) * | 2016-09-27 | 2017-01-25 | 北京奇虎科技有限公司 | Webpage caching method and device |
| CN106776761A (en) * | 2016-11-18 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | A kind of mobile browser renders the method and device of webpage |
| CN107277038A (en) * | 2017-07-18 | 2017-10-20 | 北京微影时代科技有限公司 | Access control method, device and system |
| CN108153798A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page info processing method, apparatus and system |
| CN110309456A (en) * | 2018-03-12 | 2019-10-08 | 优视科技有限公司 | A kind of page display method and device |
-
2019
- 2019-11-11 CN CN201911096162.9A patent/CN110851688A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120047445A1 (en) * | 2010-08-20 | 2012-02-23 | Salesforce.Com, Inc. | Pre-fetching pages and records in an on-demand services environment |
| CN106354879A (en) * | 2016-09-27 | 2017-01-25 | 北京奇虎科技有限公司 | Webpage caching method and device |
| CN106776761A (en) * | 2016-11-18 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | A kind of mobile browser renders the method and device of webpage |
| CN108153798A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page info processing method, apparatus and system |
| CN107277038A (en) * | 2017-07-18 | 2017-10-20 | 北京微影时代科技有限公司 | Access control method, device and system |
| CN110309456A (en) * | 2018-03-12 | 2019-10-08 | 优视科技有限公司 | A kind of page display method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112732136A (en) * | 2020-12-30 | 2021-04-30 | 五八有限公司 | Desktop component adding method, desktop component adding device and terminal equipment |
| CN114443196A (en) * | 2022-01-17 | 2022-05-06 | 苏州浪潮智能科技有限公司 | User interface processing method and system and electronic equipment |
| CN114443196B (en) * | 2022-01-17 | 2023-07-14 | 苏州浪潮智能科技有限公司 | User interface processing method and system and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108647141B (en) | Automatic test method, device, computer readable medium and electronic equipment | |
| US9203720B2 (en) | Monitoring the health of web page analytics code | |
| US10177992B2 (en) | Application store interface for remote management of client devices | |
| US8346889B1 (en) | Event-driven module loading | |
| CN104834602B (en) | A kind of program dissemination method, device and program delivery system | |
| US9912747B2 (en) | Browser and system for download and download method | |
| CN113079164B (en) | Remote control method and device for bastion machine resources, storage medium and terminal equipment | |
| CN111913738A (en) | Access request processing method, device, computing equipment and medium | |
| CN111782988A (en) | Method, device, computer system and storage medium for determining source of application program | |
| GB2508875A (en) | Defining elements of web pages for variation | |
| CN110851688A (en) | Page request method, device and equipment | |
| CN113760763A (en) | Software testing method, device, server and system | |
| CN113542418A (en) | File management method and device, electronic equipment and storage medium | |
| CN102932471A (en) | Method and system for login server by browser and for achieving browser login | |
| CN106649581B (en) | Webpage repairing method and client | |
| US10432490B2 (en) | Monitoring single content page application transitions | |
| CN116644250B (en) | Page detection method, page detection device, computer equipment and storage medium | |
| US20230350700A1 (en) | Snapshot capture of computing device user interfaces | |
| CN116756016A (en) | Multi-browser testing method, device, equipment, medium and program product | |
| CN107391132B (en) | Method, device and equipment for target App to execute preset action | |
| US7509413B2 (en) | Tool for displaying JMX monitoring information | |
| CA3141546A1 (en) | Log-based testing method, device, and computer system | |
| KR102303182B1 (en) | Automated Test Network System and Automated Test Method | |
| CN110659191B (en) | Buried data analysis method, buried data analysis device, computer equipment and storage medium | |
| CN112565472B (en) | Static resource processing method and device |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200228 |