WO2019192128A1

WO2019192128A1 - Webpage access method and apparatus

Info

Publication number: WO2019192128A1
Application number: PCT/CN2018/101555
Authority: WO
Inventors: 刘俊廷
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-04-04
Filing date: 2018-08-21
Publication date: 2019-10-10
Also published as: CN108536805A

Abstract

The present application relates to a webpage access method and apparatus. The webpage access method comprises: a front end obtains a webpage access request initiated by an Internet application to a back end; performs webpage resource location in the back end according to the webpage link address in the webpage access request, and receives a webpage resource returned by the back end, the webpage resource comprising only front-end data; performs, by means of a presentation layer separated from the back end, in the Internet application, webpage display on the webpage resource comprising only the front-end data. Use of the present webpage access method and apparatus resolves the problem in the prior art of low efficiency of webpage access due to excessive coupling of front and back ends.

Description

Webpage access method and device

Technical field

[0001] This application claims priority to the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the disclosure of

[0001] The present application relates to the field of computer technologies, and in particular, to a webpage access method and apparatus.

Background technique

[0003] With the rise of the Internet, Internet applications have emerged. The so-called Internet applications use a front-end (user-side)/back-end (server-side) communication model to provide customers with diverse needs.

[0004] Specifically, the back end is a webpage resource for storing a related webpage by the front end, and as long as data is transmitted between the front end and the back end, the webpage link address (URL) stored by the front end can be stored and stored in the back end. The webpage resource of the webpage link address, thereby realizing online access to the webpage, thereby enabling the user to enjoy various online services provided by the webpage by using the internet application.

[0005] However, in terms of data transmission between the front end and the back end, the front end and the back end are highly coupled and the maintenance cost is high.

[0006] For example, the data received by the front end is not pure enough, that is, some data that should be processed by the back end (hereinafter referred to as backend data) is included, and the front end needs to perform data format on the back end data. After the conversion, the conversion data that the front end can support is formed, and then the subsequent processing can be performed. Similarly, the data received by the backend is not pure enough. It also contains some data that should be processed by the front end (hereinafter referred to as the front end data). Data format conversion is also required before processing.

[0007] Based on this, the inventor realized that for the development stage, since the data processed by the front end includes not only the front end data but also some back end data, the development of the front end must depend on the development of the back end, and vice versa. It is said that the development of the back-end depends on the development of the front-end, that is, the coupling between the front and the back is very high, which will inevitably lead to the complexity of data format conversion during the webpage access process, which in turn leads to inefficient webpage access. Summary of invention

technical problem

Problem solution Technical solution

[0008] In order to solve the above technical problem, an object of the present application is to provide a webpage access method and device.

[0009] The technical solution adopted by the application is:

[0010] In one aspect, a method for accessing a webpage includes: acquiring, by a front end, a webpage access request initiated by an internet application to a backend; performing webpage resource location in a backend according to a webpage link address in the webpage access request, and receiving the a webpage resource returned by the back end, the webpage resource only includes front end data; and a webpage resource including only the front end data is displayed on the webpage in the internet application by a presentation layer separated from the back end

[0011] In another aspect, a webpage accessing apparatus includes: a request initiating module configured to acquire, by a front end, a webpage access request initiated by an internet application to a backend; and a resource receiving module configured to: according to a webpage link in the webpage access request The address is located in the back end to perform webpage resource location, and receives the webpage resource returned by the backend, where the webpage resource only includes the front end data; the webpage display module is configured to use the presentation layer separated from the backend to the webpage containing only the front end data. The resource displays the web page in the internet application.

[0012] In another aspect, a webpage access device includes a processor and a memory, wherein the memory stores computer readable instructions, and the computer readable instructions are executed by the processor to implement webpage access as described above. method.

[0013] In another aspect, a computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement a web page access method as described above.

[0014] In the above technical solution, since the webpage resource returned by the backend only includes the front end data, the front end receives the pure data, and the presentation layer for the webpage display is separated from the back end, thereby avoiding the coupling of the front and rear ends is too high. The utility model effectively reduces the complexity in the webpage access process, and solves the problem that the webpage access efficiency is low due to the excessive coupling of the front and rear ends in the prior art.

The above general description and the following detailed description are merely exemplary and explanatory, and are not limiting.

Advantageous effects of the invention

Brief description of the drawing

DRAWINGS [0016] The accompanying drawings, which are incorporated in FIG

1 is a schematic diagram of an implementation environment in accordance with the present application.

2 is a block diagram showing a hardware structure of a terminal according to an exemplary embodiment.

3 is a block diagram showing a hardware structure of a server according to an exemplary embodiment.

[0020] FIG. 4 is a flowchart of a webpage access method according to an exemplary embodiment.

[0021] FIG. 5 is a flowchart of another webpage access method according to an exemplary embodiment.

[0022] FIG. 6 is a flow diagram of an embodiment of step 430 of the corresponding embodiment of FIG. 5.

7 is a flow chart of another embodiment of step 430 in the corresponding embodiment of FIG. 5.

8 is a flow chart of an embodiment of step 350 in the corresponding embodiment of FIG. 4.

[0025] FIG. 9 is a block diagram of a webpage access device, according to an exemplary embodiment.

FIG. 10 is a structural block diagram of a webpage access apparatus according to an exemplary embodiment.

The present invention has been described in detail with reference to the accompanying drawings. Specific embodiments illustrate the concepts of the present application to those skilled in the art.

Invention embodiment

Embodiments of the invention

[0028] Description will now be made in detail of the exemplary embodiments, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same reference numerals The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with aspects of the present application as detailed in the appended claims.

1 is a schematic diagram of an implementation environment involved in a webpage access method. The implementation environment includes a terminal (i.e., front end) 100 and a server side (i.e., back end) 200.

[0030] The terminal 100 may be a notebook computer, a tablet computer, a smart phone, a desktop computer, or other electronic device that can be operated by an Internet application, and is not limited herein.

[0031] A communication connection is established between the terminal 100 and the server end 200, and the communication connection includes, but is not limited to, a wireless network connection, a wired network connection, etc., and then performs data transmission through the established communication connection, for example, Transfer web resources, etc. over a communication connection.

Specifically, the terminal 100 initiates a webpage access request to the server 200 by using the running internet application to obtain the webpage resource in the server 200, and then controls the webpage resource to display the webpage in the internet application.

[0033] Please refer to FIG. 2. FIG. 2 is a block diagram of a terminal according to an exemplary embodiment.

[0034] It should be noted that the terminal 100 is only an example that is suitable for the present application, and is not considered to provide any limitation on the scope of use of the present application. The terminal 100 is also not to be construed as having to rely on or must have one or more of the exemplary terminals 100 shown in FIG.

As shown in FIG. 2, the terminal 100 includes a memory 101, a memory controller 103, one or more (only one shown in FIG. 2) processor 105, a peripheral interface 107, a radio frequency module 109, a positioning module 111, The camera module 1 13 , the audio module 115 , the touch screen 117 , and the button module 119 . These components communicate with one another via one or more communication bus/signal lines 121.

[0036] The memory 101 can be used to store a computer program and a module, such as a mobile terminal-based client data security access method and a computer-readable instruction and a module corresponding to the device in the exemplary embodiment of the present application. Computer readable instructions within memory 101, thereby performing various functions and data processing, i.e., completing a mobile terminal based secure access method for customer data.

[0037] The memory 101, as a carrier for resource storage, may be a random access memory such as a high speed random access memory, a non-volatile memory such as one or more magnetic storage devices, flash memory, or other solid state memory. The storage method can be short-term storage or permanent storage.

[0038] The peripheral interface 107 may include at least one wired or wireless network interface, at least one serial-parallel conversion interface, at least one input-output interface, and at least one USB interface, etc., for calling external external input/output devices to the memory 101 and the processor 105 are configured to implement communication with various external input/output devices.

[0039] The radio frequency module 109 is configured to transmit and receive electromagnetic waves, and realize mutual conversion between electromagnetic waves and electric signals, thereby communicating with other devices through the communication network. The communication network includes a cellular telephone network, a wireless local area network, or a metropolitan area network, and the above communication networks can use various communication standards, protocols, and technologies.

[0040] The positioning module 111 is configured to acquire the geographic location where the terminal 100 is currently located. Examples of positioning module 111 include, but are not limited to, Global Positioning System (GPS), wireless local area network or mobile communication network based positioning technology. [0041] The camera module 113 is attached to the camera for taking pictures or videos. The captured picture or video can be stored in the memory 101, and can also be sent to the upper computer through the radio frequency module 109.

[0042] The audio module 115 provides an audio interface to the user, which may include one or more microphone interfaces, one or more speaker interfaces, and one or more earphone interfaces. Audio data interaction with other devices via the audio interface. The audio data can be stored in the memory 101 and can also be sent through the radio frequency module 109.

[0043] The touch screen 117 provides an input and output interface between the terminal 100 and the user. Specifically, the user can perform an input operation through the touch screen 117, such as a click, touch, slide, etc., to cause the terminal 10 to respond to the input operation. The terminal 100 displays the output content formed by any one or combination of text, picture or video to the user through the touch screen 117.

[0044] The button module 119 includes at least one button for providing an interface for the user to input to the terminal 100, and the user can cause the terminal 100 to perform different functions by pressing different buttons. For example, the sound adjustment button can be used by the user to adjust the volume of the sound played by the terminal 100.

[0045] It will be understood that the structure shown in FIG. 2 is merely illustrative, and the terminal 100 may further include more or less components than those shown in FIG. 2, or have components different from those shown in FIG. 2. The components shown in Figure 2 can be implemented in hardware, software, or a combination thereof.

FIG. 3 is a block diagram showing the hardware structure of a server 200 according to an exemplary embodiment. It should be noted that the server 200 is only an example that is adapted to the present application and is not considered to provide any limitation on the scope of use of the present application. The server 200 is also not to be construed as having to rely on or must have one or more of the exemplary servers 200 shown in FIG.

[0047] The hardware structure of the server 200 may vary greatly depending on configuration or performance. As shown in FIG. 3, the server 200 includes: a power source 210, an interface 230, at least one memory 250, and at least one central processor. (CPU, Central Processing Units) 270.

[0048] The power source 210 is configured to provide an operating voltage for each hardware device on the server 200.

The interface 230 includes at least one wired or wireless network interface 231, at least one serial-to-parallel conversion interface 233, at least one input/output interface 235, at least one USB interface 237, and the like for communicating with an external device.

[0050] The memory 250 serves as a carrier for resource storage, and may be a read only memory, a random access memory, a magnetic disk, or an optical disk. The resources stored thereon include an operating system 251, an application 253, and data 255, etc., and are stored. The mode can be short-term storage or permanent storage. The operating system 251 is used to manage and control various hardware devices and applications 253 on the server 200 to implement calculation and processing of the massive data 255 by the central processing unit 270, which may be Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM. , FreeBSDTM, etc. The application 253 is a computer program that performs at least one specific work based on the operating system 251, which may include at least one module (not shown in FIG. 3), each of which may include a series of computers to the server 200, respectively. Readable instructions. The data 255 may be a photo, a picture, or the like stored on a disk.

[0051] The central processing unit 270 can include one or more processors and is configured to communicate with the memory 250 over a bus for computing and processing the vast amount of data 255 in the memory 250.

[0052] As described in detail above, the server 200 to which the present application is applied will complete the web page access method by the central processor 270 reading a series of computer readable instructions stored in the memory 250.

Furthermore, the present application can also be implemented by a hardware circuit or a hardware circuit in combination with software. Therefore, the implementation of the present application is not limited to any specific hardware circuit, software, or a combination of both.

Referring to FIG. 4, in an exemplary embodiment, a webpage access method is applicable to the terminal of the implementation environment shown in FIG. 1, and the structure of the terminal may be as shown in FIG. 2.

[0055] The webpage access method may be performed by a terminal (ie, a front end), and may include the following steps:

[0056] Step 310: The front end acquires a webpage access request initiated by the internet application to the back end.

[0057] As mentioned above, Internet applications use a front-end/back-end communication model to provide customers with diverse needs. For example, the back end is a webpage resource for storing a related webpage at the front end, and as long as the front end interacts with the back end, the webpage resource in the backend can be obtained, thereby realizing online access of the webpage by the user, thereby enabling the user to enjoy the webpage by using the internet application. A variety of online services are available.

[0058] Thus, the webpage access request is initiated by the user to control the internet application running on the front end to perform online access to the webpage. The webpage access request indicates the webpage requested by the internet application, so that the backend can return the webpage resource requested by the internet application to access the webpage. For example, the internet application can be an insurance marketing application, and the web page can be a policy sales web page or a policy after-sales web page.

[0059] It should be understood that the webpage resources of the webpage stored in the backend are massive, and the storage locations of different webpage resources are different. Therefore, the webpage access request is generated based on the storage location of the webpage resource, and can also be understood. For example, the webpage access request carries the storage location of the webpage resource.

[0060] The webpage link address, that is, the storage location indicating the webpage resource, is used to locate the webpage resource in the backend. That is to say, different webpage resources have different webpage link addresses, that is, the webpage link address realizes unique identification of the storage location of the webpage resource in the backend, thereby being able to uniquely obtain the backend based on the webpage link address. Stored web resources.

[0061] Step 330: Perform webpage resource location in the backend according to the webpage link address in the webpage access request, and receive the webpage resource returned by the backend.

[0062] For the backend, after receiving the webpage access request sent by the front end, the webpage link address is extracted from the webpage access request, and the webpage resource can be located according to the webpage link address.

[0063] The positioning, that is, the storage location corresponding to the massive webpage resource stored in the backend, is searched according to the storage location of the webpage resource indicated by the webpage link address, to obtain the webpage resource stored in the storage location.

[0064] For the front end, when the back end returns the webpage resource, the webpage resource is received accordingly. The web resource contains only front-end data.

[0065] The webpage resource only includes the front-end data, which means that the data received by the front-end is pure, that is, does not include the back-end data, and can also be understood that the data received by the front end does not have data that should be processed by the backend. In this way, the purpose of separating the front and rear ends is achieved.

[0066] Step 350: Perform a webpage display in an internet application by using a presentation layer separated from the backend to a webpage resource containing only frontend data.

[0067] wherein the so-called presentation layer indicates the form of the presentation web page resource.

[0068] For example, if the webpage resource is text, the presentation form of the webpage resource indicated by the presentation layer may be a txt format, so that the text is displayed in the txt format in the internet application, or the webpage resource is a picture, and the presentation layer is The indicated web resource may be in the jpg format, so that the web application displays the image through the j pg format.

[0069] It can be understood that the webpage display is mainly performed in the front end. Therefore, in this embodiment, the presentation layer is separated from the backend.

[0070] Specifically, in the data development in which the front end is independent of the back end, since the developed data may be transmitted to The back end decouples the developed data from the presentation layer for web page display to form a presentation layer separate from the back end.

[0071] In other words, the presentation layer separated from the back end is completely maintained by the front end, and does not need to depend on the back end. Accordingly, the data independently developed by the front end received by the back end will not exist. The processed data (for example, presentation layer related data) is used to further achieve the purpose of separation of the front and rear ends.

[0072] In the foregoing implementation process, the decoupling of the front and the rear ends is realized by the webpage resource including only the front end data and the presentation layer separated from the back end, so that the complexity in the webpage access process is effectively reduced, thereby solving the existing In the technology, the problem of low efficiency of webpage access due to excessive coupling between front and rear ends.

Referring to FIG. 5, in an exemplary embodiment, before step 330, the foregoing method may further include the following steps:

[0074] Step 410: The back end performs data development independently of the front end to generate a webpage resource.

[0075] wherein the webpage resource only includes front-end data conforming to a standard data format.

[0076] Step 430: Deploy a communication interface in the back end for data independent development to perform transmission of the webpage resource through the communication interface.

[0077] That is to say, in the data development in which the back end is independent of the front end, since the webpage resource is used for displaying the webpage in the front end and needs to be transmitted to the front end, the generated webpage resource only includes the front end data, and thus the front end is The received data is pure, so as to achieve separation between the front and rear ends.

[0078] Optionally, because the front and rear ends are separated, the data interaction between the front end and the back end is implemented through a unified communication interface, which not only reduces the complexity of data transmission, but also facilitates subsequent data format conversion, thereby further facilitating further Improve web page access efficiency.

[0079] The standard data format is configured by the communication interface, that is, the standard data formats supported by different communication interfaces are different, and the standard data format configured for the front-end data is also different. For example, the communication interface is an API interface, and correspondingly, the standard data format configured for the front end data may be JSON, XML, or the like.

[0080] In a specific implementation of an embodiment, the API interface is a restful style for the backend.

[0081] As shown in FIG. 6, step 430 may include the following steps:

[0082] Step 431: Perform communication protocol configuration of the API interface.

[0083] After a unified API interface is deployed on the front and rear ends, a communication protocol is configured for the unified API interface, so that the unified API interface conforms to the configured communication protocol when performing data transmission, thereby achieving high efficiency. Data transfer.

[0084] For example, the communication protocol is the http protocol or the https protocol.

[0085] Step 433: Perform domain name deployment on an API interface configured with a communication protocol.

[0086] The domain name is uniquely identified by the location (electronic location/geographical location) where the backend is located, for example, the front end directly accesses the backend through the domain name.

[0087] The domain name deployment means that the API interface configured with the communication protocol is deployed in the domain name, so that the access is based on the API interface deployed in the domain name. For example, the front end directly accesses the API of the back end through the API interface deployed by the domain name. interface.

Specifically, the domain name is deployed, and the API interface configured with the communication protocol is deployed to the primary domain name, or the API interface configured with the communication protocol may be deployed to the next domain name for the API interface that is not extended. In the class.

[0089] For example, for https://apil.example.com, the API interface is the apil interface, and the communication protocol configured for the apil interface is the https protocol. The apil interface configured with the https protocol is deployed in the primary domain name example. in _° c 0111

[0090] For http://example.org/api2/, the API interface is an api2 interface, and the communication protocol configured for the api2 interface is the http protocol, and the api2 interface configured with the http protocol is deployed under the primary domain name. In the first level.

[0091] It is added here that the API interface is essentially an interface provided by the operating system to the application, thereby causing the application to trigger the operating system to execute the application instruction by calling the API interface, thereby, according to the application instruction The calling service provided by the API interface also changes. If the calling service provided by the API interface is relatively simple and fixed, the API interface is regarded as an API interface that does not extend.

[0092] Step 435: Add a path and an operation type of the webpage resource in the domain name in which the API interface is deployed.

[0093] The path of the webpage resource indicates the storage location of the webpage resource in the backend, so that the frontend can access the corresponding webpage resource stored in the backend through the path of the webpage resource in the domain name.

[0094] The operation type refers to an operation that the backend can perform on a webpage resource, including but not limited to: resource extraction, resource creation, resource update, resource deletion, and the like.

[0095] Optionally, as shown in FIG. 7, step 430 may further include the following steps:

[0096] Step 437: Add filtering information to the domain name where the API interface is deployed. [0097] If there are too many webpage resources, the backend cannot return all the webpage resources to the front end. For this reason, the filtering information is used for filtering the webpage resources, and the filtering information includes but is not limited to: return quantity, filter condition, return The starting position of the web resource, the sort order of the returned web resources, and so on.

[0098] Step 439: Add status code information to the domain name where the API interface is deployed.

[0099] The status code information includes a status code returned by the back end to the front end, thereby indicating the result of the operation and/or operation performed by the back end on the web resource.

[0100] For example, if the status code is 200, it indicates that the backend returns the requested webpage resource successfully to the front end, or the status code is 400, indicating that the backend does not perform a new operation or an update operation of the webpage resource.

[0101] Through the cooperation of the foregoing embodiments, the restful style API interface deployment in the backend is implemented, thereby providing a basis for the front end to access the webpage, that is, the front end can request the backend through the domain name including the restful style API interface. Returns the corresponding web resource of the web page.

[0102] It should be noted that the order of execution of steps 437 to 439 may be adjusted, and this embodiment is not limited thereto.

[0103] In an exemplary embodiment, before step 350, the foregoing method may further include the following steps:

[0104] In the data development in which the front end is independent of the back end, the developed data is decoupled from the presentation layer for web page display to form a presentation layer separate from the back end.

[0105] Decoupling refers to separating the presentation layer for web page display from the data developed by the front end, so that the data transmitted to the back end does not include presentation layer related data for web page display, so that the back end receives the data. The data is pure, that is, there is no data that should be processed by the front end, for example, data related to the presentation layer for web page display.

[0106] Software architecture used for decoupling, including but not limited to: MVC (Model-View-Controller), MVP (Model-View-Presenter), MVVM (Model-View-Vie wModel) mode.

[0107] In an exemplary embodiment, before step 350, the foregoing method may further include the following steps:

[0108] The front end performs component packaging on the presentation layer separated from the back end.

[0109] It should be understood that in the webpage display process, in addition to the display of the webpage resources, the presentation of the interface elements is also involved, for example, the interface elements include a menu bar, a taskbar, a view button, and the like. Correspondingly, the presentation layer separate from the backend, in addition to indicating the representation of the web page resource, will also indicate the display style of the interface element.

[0110] Thus, in this embodiment, the component encapsulation performed by the presentation layer refers to the componentization of the interface elements. The same interface element has a unified display style in the webpage display process through the presentation layer, which not only simplifies the complexity of the presentation layer development, but also enhances the flexibility and aesthetics of the interface element, thereby facilitating the user's access experience.

[0111] In an application scenario, the same softphone dialing button in the policy sales page and the policy after-sales page is uniformly packaged as component A, and the component A is displayed by the phone icon, thereby making the policy sales page and the policy after-sales page The softphone dial button is displayed as a phone icon during web page display.

Referring to FIG. 8, in an exemplary embodiment, step 350 may include the following steps:

[0113] Step 351: The front end receives the webpage resource through the communication interface deployed by the front end, and obtains the webpage resource that only includes the front end data conforming to the standard data format.

[0114] As described above, since the front and rear ends are separated, the data interaction between the front end and the back end is realized through a unified communication interface, which not only reduces the complexity of data transmission, but also facilitates subsequent data format conversion, thereby facilitating further Improve the efficiency of web page access.

[0115] Thus, the communication interface deployed by the front end is consistent with the back end. For example, the communication interface is an API interface. Accordingly, the standard data format is configured by the API interface, including but not limited to: JSON, XML, and the like.

[0116] In a specific implementation of an embodiment, for the front end, after the backend returns the webpage resource through the restful-style API interface, the front-end data conforming to the JSON format can be received.

[0117] Step 353: Perform data format conversion on the front end data conforming to the standard data format in the webpage resource, and obtain conversion data.

[0118] Data format conversion means that the standard data format of the front end data is converted into a data format supported by the front end actual processing.

[0119] Step 355: Calling a presentation layer separated from the back end in the Internet application to perform webpage display according to the converted data

[0120] In the above process, the received webpage resource only includes front-end data conforming to the standard data format, that is, there is no data that should be processed by the backend, and it can be understood that the data received by the front-end is pure. Therefore, in the web page display process performed by the presentation layer separated from the back end, the front end only needs to process the front end data, avoiding processing the back end data, thereby improving the front end processing efficiency, thereby accelerating the web page display process, and facilitating user access. Experience. [0121] The following is an apparatus embodiment of the present application, which may be used to perform a mobile terminal-based client data security access method according to the present application. For details not disclosed in the embodiment of the present application, refer to the method embodiment of the mobile terminal-based client data security access method according to the present application.

Referring to FIG. 9, in an exemplary embodiment, a webpage access device 900 includes, but is not limited to, a request initiation module 910 resource receiving module 930 and a web page display module 950.

[0123] The request initiating module 910 is configured to obtain, by the front end, a webpage access request initiated by the internet application to the back end.

[0124] The resource receiving module 930 is configured to perform webpage resource location in the backend according to the webpage link address in the webpage access request, and receive the webpage resource returned by the backend, and the webpage resource only includes the frontend data.

[0125] The webpage display module 950 is configured to perform webpage display in an internet application on a webpage resource including only front-end data through a presentation layer separated from the backend.

[0126] It should be noted that, when performing the webpage access processing, the webpage accessing device provided in the above embodiment is only exemplified by the division of the above functional modules. In actual applications, the foregoing functional allocation may be different according to needs. The function module is completed, that is, the internal structure of the webpage access device is divided into different functional modules to complete all or part of the functions described above.

[0127] In addition, the webpage accessing device and the webpage accessing method provided by the foregoing embodiments are in the same configuration, and the specific manner in which each module performs the operation has been described in detail in the method embodiment, and details are not described herein again.

Referring to FIG. 10, in an exemplary embodiment, a webpage access device 1000 includes a processor 1001 and a memory 1004. The device 1000 also includes a communication interface 1002 and a communication bus 1003. The processor 1001 reads the computer readable instructions stored in the memory 1004 via the communication bus 1003.

[0129] The memory 1004 stores computer readable instructions, which are executed by the processor 1001 to implement the webpage access method in the foregoing embodiments.

[0130] In an exemplary embodiment, a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the web page access method of the above embodiments.

The above is only a preferred exemplary embodiment of the present application, and is not intended to limit the embodiments of the present application. Those skilled in the art can make corresponding modifications in a very convenient manner according to the main concepts and spirit of the present application. Or modify, so the scope of protection of this application shall be subject to the scope of protection required by the claims. 

Claims

Claim

[Claim 1] A webpage access method, wherein the method includes:

The front end obtains a webpage access request initiated by the internet application to the back end; the webpage resource is located in the backend according to the webpage link address in the webpage access request, and the webpage resource returned by the backend is received, and the webpage resource only includes the front end Data; displaying a web page in the Internet application through a presentation layer separate from the back end to a web page resource containing only front end data.

[Claim 2] The method of claim 1, wherein the webpage resource location is located in the backend according to the webpage link address in the webpage access request, and the webpage resource returned by the backend is received. The method also includes:

The back end performs data development independently of the front end to generate a webpage resource, and the webpage resource only includes front end data conforming to a standard data format;

A communication interface is deployed in the back end for data independent development to transmit the webpage resource through the communication interface.

[Claim 3] The method according to claim 2, wherein the communication interface is a restful style API connection

The deploying the communication interface in the back end for performing data independent development includes: performing communication protocol configuration of the API interface;

Performing domain name deployment on the API interface configured with the communication protocol;

Adding the path and operation type of the webpage resource in the domain name in which the API interface is deployed

[Claim 4] The method of claim 3, wherein the deploying the communication interface in the back end of the data independent development further includes:

Adding filtering information to the domain name in which the API interface is deployed, where the filtering information is used for filtering the webpage resource; and/or

The status code information is added to the domain name in which the API interface is deployed, and the status code information is used to indicate the execution result and/or operation execution result performed by the back end on the webpage resource.

[Claim 5] The method according to any one of claims 1 to 4, wherein the table separated from the back end The method further includes: before the webpage resource that includes only the front-end data is displayed on the webpage in the Internet application, the method further includes:

In the data development performed by the front end independently of the back end, the developed data is decoupled from the presentation layer for web page display to form a presentation layer separate from the back end.

[Claim 6] The method according to any one of claims 1 to 5, wherein, by the presentation layer separated from the back end, before the webpage resource including only the front end data is displayed on the webpage in the internet application, The method further includes:

The front end performs component packaging on a presentation layer separated from the back end.

[Claim 7] The method according to any one of claims 1 to 6, wherein the presentation layer separated from the back end displays a web page in the Internet application for a webpage resource including only front end data, including :

The front end receives the webpage resource through the communication interface deployed by the front end, and obtains a webpage resource that only includes the front end data conforming to the standard data format;

Performing data format conversion on the front end data conforming to the standard data format in the webpage resource to obtain converted data;

In the Internet application, a presentation layer separated from the backend is called to perform webpage display according to the converted data.

[Claim 8] A webpage access device, wherein the device includes:

The request initiation module is configured to obtain, by the front end, a webpage access request initiated by the internet application to the back end;

The resource receiving module is configured to perform webpage resource location in the back end according to the webpage link address in the webpage access request, and receive the webpage resource returned by the backend, where the webpage resource only includes front end data;

The webpage display module is configured to display the webpage in the internet application through a presentation layer separate from the backend to a webpage resource containing only frontend data.

[Claim 9] The device according to claim 8, wherein the device further comprises:

a resource generation module, configured to perform data development independently of the front end, and generate a webpage resource, where the webpage resource only includes front end data conforming to a standard data format; The interface deployment module is configured to deploy a communication interface in the back end for data independent development to transmit the webpage resource through the communication interface.

[Claim 10] The device according to claim 9, wherein the communication interface is a restful style API connection

The interface deployment module includes:

a protocol configuration unit configured to perform a communication protocol configuration of the API interface; a domain name deployment unit configured to perform domain name deployment on the API interface configured with the communication protocol;

An interface adding unit is configured to add a path and an operation type of the webpage resource in a domain name in which the API interface is deployed.

[Claim 11] The device of claim 10, wherein the interface deployment module further comprises:

The first information adding unit is configured to add filtering information to the domain name in which the API interface is deployed, where the filtering information is used for filtering the webpage resource; and/or the second information adding unit is configured to be deployed. The status code information is added to the domain name of the API interface, and the status code information is used to indicate the execution result and/or operation execution result performed by the back end on the webpage resource.

[Claim 12] The device according to any one of claims 8 to 11, wherein the device further comprises:

The presentation layer forming module is configured to decouple the developed data from the presentation layer for displaying the web page in a data development in which the front end is independent of the back end, and form a presentation layer separated from the back end.

[Claim 13] The device according to any one of claims 8 to 12, wherein the device further comprises:

And a component encapsulation module configured to perform component packaging on the presentation layer separated from the back end by the front end.

The device of any one of claims 8 to 13, wherein the webpage display module includes a resource acquisition unit, configured to receive, by the front end, a webpage resource through a communication interface deployed by the front end, and obtain only a webpage resource including a front end data conforming to a standard data format; a format conversion unit configured to count the number of front ends in the webpage resource conforming to a standard data format According to the data format conversion, the converted data is obtained;

And a display unit configured to invoke a presentation layer separated from the back end in the Internet application to perform webpage display according to the converted data.

[Claim 15] A webpage access device, wherein the device comprises:

Processor; and

a memory, the computer readable instructions being stored thereon, the computer readable instructions being executed by the processor by the following steps:

The device of claim 15, wherein the step of performing web resource location in the backend according to the webpage link address in the webpage access request, before receiving the webpage resource returned by the backend, The processor also performs the following steps:

[Claim 17] The device of claim 16, wherein the communication interface is a restful-style API interface;

In the step of deploying a communication interface in the back end for data independent development, the processor performs the following steps:

Performing a communication protocol configuration of the API interface;

[Claim 18] The apparatus according to claim 17, wherein the said In the step of deploying the communication interface in the end, the processor further performs the following steps: adding filtering information to the domain name in which the API interface is deployed, where the filtering information is used for filtering the webpage resource; and/or

[Claim 19] The apparatus according to any one of claims 15 to 18, wherein the presentation layer separated from the back end pairs the webpage resource including only the front end data before the webpage display step in the internet application The processor also performs the following steps:

[Claim 20] The device according to any one of claims 15 to 19, wherein the presentation layer separated from the back end before the web page display step in the Internet application is performed on the webpage resource including only the front end data The processor also performs the following steps:

[Claim 21] The device according to any one of claims 15 to 20, wherein the presentation layer separated from the back end performs a web page display step in the Internet application by using a webpage resource including only front end data The processor performs the following steps:

[Claim 22] A computer readable storage medium having stored thereon a computer program, wherein the computer program is executed by a processor by the following steps:

The front end obtains a webpage access request initiated by the internet application to the back end; the webpage resource is located in the backend according to the webpage link address in the webpage access request, and the webpage resource returned by the backend is received, and the webpage resource only includes the front end data; The webpage display is performed in the internet application by a presentation layer separated from the backend to a webpage resource containing only front-end data.

The computer readable storage medium according to claim 22, wherein the webpage resource location is performed in the backend according to the webpage link address in the webpage access request, and the webpage returned by the backend is received. Before the resource step, the processor further performs the following steps: the back end performs data development independently of the front end, and generates a webpage resource, where the webpage resource only includes front end data conforming to a standard data format;

[24] The computer readable storage medium of claim 23, wherein the communication interface is a re stful style API interface;

Performing a communication protocol configuration of the API interface;

[Claim 25] The computer readable storage medium according to claim 24, wherein in the step of deploying a communication interface in the back end for data independent development, the processor further performs the following steps:

The computer readable storage medium according to any one of claims 22 to 25, wherein the presentation layer separated from the back end performs web page resources including only front end data in the internet application Before the step of displaying the webpage, the processor further performs the following steps: the front end is independent of the data development performed by the back end, and the developed data is used for the network. The presentation layer of the page display is decoupled to form a presentation layer separate from the back end.

The computer readable storage medium according to any one of claims 22 to 26, wherein the presentation layer separated from the back end performs web page resources including only front end data in the internet application Before the step of displaying the web page, the processor further performs the following steps: the front end performs component packaging on a presentation layer separated from the back end.

[Claim 28] The computer readable storage medium according to any one of claims 22 to 27, wherein the presentation layer separated from the back end performs web page resources including only front end data in the Internet application In the web page display step, the processor performs the following steps: