Cross-domain file request method and device, and service system

Abstract

The application discloses a cross-domain file request method and device and a business service system, and relates to big data. The method comprises the following steps: receiving a file request for transmitting a cross-domain file requested by a user through a front-end page of a browser; detecting whether the browser supports a cross-domain protocol; in the case that the browser supports the cross-domain protocol, sending the file request to a first server to access a file processing micro-service server, so that the file processing micro-service server processes the file request; and in the case that the browser does not support the cross-domain protocol, sending the file request to a second server, wherein the second server is homologous to the front-end page, the second server is connected with a plurality of micro-service servers, the plurality of micro-service servers comprise the file processing micro-service server, and the second server is used for accessing the file processing micro-service server through a reverse proxy to make the file processing micro-service server process the file request. The application can improve the response speed of file processing.

Description

Technical Field

[0001] This invention relates to the field of big data technology, and in particular to a cross-domain file request method and apparatus, and a business service system. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] With the development of internet technology, users' demand for uploading and downloading files on the network has increased. When a user uploads or downloads a file in a browser, the browser will determine the service address the page is trying to access. If the service address complies with the same-origin policy, that is, the protocol, domain name, and port of the service address are the same, it can be accessed directly. Otherwise, if the protocol, domain name, and port of the service address are not completely consistent, the browser will not allow cross-origin access under normal circumstances for security reasons. Summary of the Invention

[0004] This invention provides a cross-domain file request method to improve file processing response speed. The method includes:

[0005] Receive file requests from users via the browser's front-end page to transfer cross-domain files;

[0006] Check if the browser supports cross-domain protocols;

[0007] If the browser supports cross-domain protocols, a file request is sent to the first server; the first server is not from the same origin as the front-end page and supports cross-domain protocols; the first server connects to the file processing microservice server to access the file processing microservice server so that the file processing microservice server can process the file request; the file processing microservice server is not from the same origin as the front-end page.

[0008] In cases where the browser does not support cross-domain protocols, a file request is sent to a second server. This second server is from the same origin as the front-end page and is connected to multiple microservice servers, including a file processing microservice server. The second server is used to access the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file request.

[0009] Optionally, receiving a file request from a user via a browser's front-end page to transfer cross-domain files includes:

[0010] Based on the user's actions on the front-end page, parse the business services required for the actions;

[0011] When file transfer services are included in the business services, a file request is generated.

[0012] Optionally, before receiving a file request from a user requesting the transfer of a cross-domain file via a browser's front-end page, the method further includes:

[0013] Add the first server to the whitelist of access addresses for the file processing microservice server.

[0014] This invention also provides a cross-domain file request apparatus to improve the response speed of file processing. The apparatus includes:

[0015] The receiving unit is used to receive file requests from users through the browser's front-end page to transmit cross-domain files;

[0016] The detection unit is used to detect whether the browser supports cross-domain protocols.

[0017] The first sending unit is used to send a file request to the first server when the browser supports cross-domain protocols; wherein the first server and the front-end page are not from the same origin and support cross-domain protocols; the first server is connected to the file processing microservice server and is used to access the file processing microservice server so that the file processing microservice server can process the file request; the file processing microservice server and the front-end page are not from the same origin.

[0018] The second sending unit is used to send file requests to the second server when the browser does not support cross-domain protocols. The second server is from the same origin as the front-end page and is connected to multiple microservice servers, including a file processing microservice server. The second server is used to access the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file requests.

[0019] This invention also provides a business service system to improve the response speed of file processing. The system includes:

[0020] Multiple microservice servers, each serving a corresponding microservice; these microservice servers include a file processing microservice server.

[0021] The first server, connected to the file processing microservice server, receives file requests from browsers that support cross-domain protocols and responds to file requests by accessing the file processing microservice server to process the file requests. The file requests are requests from users to transfer cross-domain files through the browser's front-end page. The first server and the file processing microservice server are not from the same origin as the front-end page.

[0022] The second server connects to multiple microservice servers to receive file requests from browsers that do not support cross-domain protocols. In response to file requests, it accesses the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file requests. The second server is from the same origin as the front-end page.

[0023] Optionally, the first server is an Apache server.

[0024] Optionally, the second server is a website web server.

[0025] Optionally, the file processing microservice server is a JBoss server cluster.

[0026] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described cross-domain file request method.

[0027] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned cross-domain file request method.

[0028] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned cross-domain file request method.

[0029] In this embodiment of the invention, after receiving a file request from a user requesting cross-domain file transfer via a browser's front-end page, the system checks whether the browser supports cross-domain protocols. If the browser supports cross-domain protocols, the system sends the file request to a first server connected to a file processing microservice server. The first server accesses the file processing microservice server, enabling it to process the file request. Both the first server and the file processing microservice server are not from the same origin as the front-end page, and the first server supports cross-domain protocols. If the browser does not support cross-domain protocols, the system sends the file request to a second server from the same origin as the front-end page. The second server is connected to multiple microservice servers, including the file processing microservice server. The second server can access the file processing microservice server through a reverse proxy, enabling it to process the file request. Compared to existing technologies, separating the cross-domain file transfer request from other requests and centrally processing the file transfer through the file processing microservice server improves file processing speed and response time. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0031] Figure 1 This is a schematic diagram of the structure of a business service system provided in an embodiment of the present invention;

[0032] Figure 2 This is a schematic diagram illustrating an application scenario of a business service system provided in an embodiment of the present invention;

[0033] Figure 3 This is a flowchart illustrating a cross-domain file request method provided in an embodiment of the present invention. Figure 1 ;

[0034] Figure 4 This is a flowchart illustrating a cross-domain file request method provided in an embodiment of the present invention. Figure 2 ;

[0035] Figure 5 This is a schematic diagram of a cross-domain file request device provided in an embodiment of the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0037] This invention provides a business service system, such as... Figure 1 As shown, the business service system includes multiple microservice servers 50, a first server 51, and a second server 52, wherein the multiple microservice servers include a file processing microservice server 501 and other microservice servers 502.

[0038] Each of the multiple microservice servers 50 is used to provide a corresponding microservice. For example, file processing microservice server 501 is used to provide file processing services, and each of the other microservice servers 502 can also provide a corresponding microservice, which will not be elaborated further here. Optionally, file processing microservice server 501 can be a JBoss server cluster.

[0039] Microservice architecture is a variation of Service-Oriented Architecture (SOA), a software development technique that divides a single application into a set of small services, each a microservice. These microservices coordinate and cooperate with each other to provide the final service to the user. Each microservice is built around a specific business function and can be independently deployed to production environments, pre-production environments, etc., and can run in its own independent process.

[0040] The first server 51 is connected to the file processing microservice server 501, and this connection can be a network connection. Servers can access each other via the network connection. The first server 51 is used to receive file requests sent by browsers that support cross-domain protocols, and in response to the file requests, accesses the file processing microservice server 501 so that the file processing microservice server 501 can process the file requests. The file request is a request from a user to transfer cross-domain files through a browser's front-end page. The front-end page is the page seen by the user in the browser, which can fulfill various service requests required for business functions.

[0041] Server 51 and file processing microservice server 501 are not from the same origin as the front-end page. The front-end page is provided by a website, and "not from the same origin" means that the protocol, domain name, and port of the website providing the front-end page are not entirely consistent with its address. When a browser discovers that the service address accessed by the same page is not from the same origin (i.e., it does not comply with the same-origin policy), for security reasons, the browser does not allow direct cross-origin access. However, if the browser supports cross-origin protocols, it can connect to a server that also supports cross-origin protocols. The cross-origin protocol can be the Cross-Origin Resource Sharing (CORS) protocol.

[0042] Therefore, in this embodiment of the invention, the first server 51 supports cross-domain protocols. Thus, if the browser also supports cross-domain protocols, the front-end page can send a configuration file request to the first server 51, thereby issuing a non-same-origin file request. After receiving the file request, the first server 51 can access the file processing microservice server 501 to process the file request. The file request is used to request the transfer (upload or download) of a cross-domain file. Optionally, the first server 51 can be an Apache server.

[0043] The second server 52 connects to multiple microservice servers 50 and is used to receive file requests sent by browsers that do not support cross-domain protocols. In response to file requests, it accesses the file processing microservice server 501 through a reverse proxy, enabling the file processing microservice server 501 to process the file requests. The second server 52 is from the same origin as the front-end page. There are no same-origin restrictions between servers; access is possible via network connection or proxy configuration. Therefore, although the second server 52 is not from the same origin as the file processing microservice server 501, it can still be accessed. Optionally, the second server 52 can be a website web server.

[0044] The implementation method of the business service system provided in this embodiment of the invention in an application scenario is as follows: Figure 2 As shown. Digitalized corporate banking services, such as bulk transfers, payroll processing, and report downloads, all involve file uploads and downloads. Large file transfers consume significant service bandwidth, potentially impacting the normal execution of other requests. For Figure 2 The business service system shown in the diagram establishes a network connection between the file request server (first server) and the file processing microservice server before application. A proxy configuration is added to the file processing microservice server via the web front-end server (second server). The address configuration for the file request server is added to the front-end project, enabling the file processing microservice server to support the CORS protocol. The file request server is also added to the address whitelist. Furthermore, a check is added to the front-end project to determine whether the currently used browser supports the CORS protocol. For browsers that do not support CORS, the file request is sent to the web front-end server address; otherwise, the file request is sent to the file request server.

[0045] like Figure 2As shown, users can access the business's front-end page through a browser. When a user performs an operation on this front-end page and issues a business request, the request may include a file request for uploading or downloading a file. If the browser supports the CORS cross-domain protocol, it can request a file request server (an Apache server) that is not from the same origin as the front-end page but also supports CORS. The file request server can directly access the file processing microservice server via a network connection. If the browser does not support CORS, it requests a web front-end server from the same origin as the front-end page. This front-end server connects to microservice servers for multiple business modules, including a transfer module microservice server, a payroll microservice server, and other module microservice servers. It accesses the file processing microservice server through a reverse proxy. Thus, after receiving a file request from the browser, the web front-end server can access the file processing microservice server via a reverse proxy. This embodiment of the invention decouples file service requests from other web service requests. By setting up a separate file processing microservice server to handle file requests, the bandwidth pressure on other web service requests is greatly reduced. This not only distributes bandwidth across different requests but also ensures a wider range of browser compatibility.

[0046] In this embodiment of the invention, after receiving a file request from a user requesting cross-domain file transfer via a browser's front-end page, the system checks whether the browser supports cross-domain protocols. If the browser supports cross-domain protocols, the file request is sent to a first server connected to a file processing microservice server. The first server accesses the file processing microservice server, enabling it to process the file request. Both the first server and the file processing microservice server are not from the same origin as the front-end page, and the first server supports cross-domain protocols. If the browser does not support cross-domain protocols, the file request is sent to a second server from the same origin as the front-end page. The second server is connected to multiple microservice servers, including the file processing microservice server. The second server can access the file processing microservice server through a reverse proxy, enabling it to process the file request. Compared to existing technical solutions, by separating the request for cross-domain file transfer from other requests and centrally processing file transfer through the file processing microservice server, the file processing speed and response speed can be improved. Furthermore, this method is applicable to browsers that do not support cross-domain protocols.

[0047] This invention provides a method for cross-domain file requests. Figure 3 This illustration shows a flowchart of a cross-domain file request method provided by an embodiment of the present invention. Figure 1 .like Figure 3As shown, the method may include the following steps:

[0048] Step 101: Receive the user's request to transfer cross-domain files through the browser's front-end page.

[0049] Users can access the front-end page providing business services by opening a browser on electronic devices such as mobile phones and computers. Users can send requests through specified operations, such as clicking a button for a certain business function. The front-end page can parse the request through scripts, analyze the various microservices required by the business function, and send a file request when a request is needed to transfer (transfer includes uploading and downloading) cross-domain files.

[0050] Step 102: Check if the browser supports cross-domain protocols.

[0051] The script on the front-end page is pre-written to detect whether the browser supports cross-domain protocols after receiving a file request. If the browser is found to support cross-domain protocols, step 103 is executed; otherwise, step 104 is executed.

[0052] Step 103: If the browser supports cross-domain protocols, send a file request to the first server. The first server is not from the same origin as the front-end page and supports cross-domain protocols; the first server is connected to the file processing microservice server to access the file processing microservice server so that the file processing microservice server can process the file request; the file processing microservice server is not from the same origin as the front-end page.

[0053] Step 104: If the browser does not support cross-domain protocols, send a file request to the second server. The second server is from the same origin as the front-end page and is connected to multiple microservice servers, including a file processing microservice server. The second server accesses the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file request.

[0054] Steps 103 and 104 can be referenced as follows: Figure 1 and Figure 2 The description of the file request processing flow of the business service system shown is not repeated here.

[0055] Optionally, the step of receiving a file request from a user via a browser's front-end page to transfer cross-domain files may include, for example: Figure 4 The following steps are shown:

[0056] Step 201: Based on the user's actions on the front-end page, parse the business services required for the operation.

[0057] Step 202: If the business service includes a file transfer service, generate a file request.

[0058] Before receiving file requests from users requesting cross-domain file transfers via the browser's front-end page, the file processing microservice server can be configured to be accessible by the first server by adding the first server to the access address whitelist of the file processing microservice server.

[0059] In this embodiment of the invention, after receiving a file request from a user requesting cross-domain file transfer via a browser's front-end page, the system checks whether the browser supports cross-domain protocols. If the browser supports cross-domain protocols, the file request is sent to a first server connected to a file processing microservice server. The first server accesses the file processing microservice server, enabling it to process the file request. Both the first server and the file processing microservice server are not from the same origin as the front-end page, and the first server supports cross-domain protocols. If the browser does not support cross-domain protocols, the file request is sent to a second server from the same origin as the front-end page. The second server is connected to multiple microservice servers, including the file processing microservice server. The second server can access the file processing microservice server through a reverse proxy, enabling it to process the file request. Compared to existing technical solutions, by separating the request for cross-domain file transfer from other requests and centrally processing file transfer through the file processing microservice server, the file processing speed and response speed can be improved. Furthermore, this method is applicable to browsers that do not support cross-domain protocols.

[0060] This invention also provides a cross-domain file request apparatus, as described in the following embodiments. Since the problem solved and the principle of this apparatus are similar to the cross-domain file request method provided in this invention, the implementation of this apparatus can refer to the implementation of the cross-domain file request method, and repeated details will not be elaborated further.

[0061] Figure 5 This is a schematic diagram of the structure of a cross-domain file request device provided in an embodiment of the present invention, such as... Figure 5 As shown, the device includes a receiving unit 10, a detection unit 20, a first transmitting unit 30, and a second transmitting unit 40.

[0062] The receiving unit 10 is used to receive a file request from a user requesting the transfer of a cross-domain file through a browser's front-end page; the detection unit 20 is used to detect whether the browser supports cross-domain protocols; the first sending unit 30 is used to send a file request to a first server when the browser supports cross-domain protocols; wherein, the first server and the front-end page are not from the same origin and support cross-domain protocols; the first server is connected to a file processing microservice server and is used to access the file processing microservice server so that the file processing microservice server processes the file request; the file processing microservice server and the front-end page are not from the same origin; the second sending unit 40 is used to send a file request to a second server when the browser does not support cross-domain protocols, wherein the second server and the front-end page are from the same origin, the second server is connected to multiple microservice servers, including the file processing microservice server, and the second server is used to access the file processing microservice server through a reverse proxy so that the file processing microservice server processes the file request.

[0063] In this embodiment of the invention, after receiving a file request from a user requesting cross-domain file transfer via a browser's front-end page, the system checks whether the browser supports cross-domain protocols. If the browser supports cross-domain protocols, the file request is sent to a first server connected to a file processing microservice server. The first server accesses the file processing microservice server, enabling it to process the file request. Both the first server and the file processing microservice server are not from the same origin as the front-end page, and the first server supports cross-domain protocols. If the browser does not support cross-domain protocols, the file request is sent to a second server from the same origin as the front-end page. The second server is connected to multiple microservice servers, including the file processing microservice server. The second server can access the file processing microservice server through a reverse proxy, enabling it to process the file request. Compared to existing technical solutions, by separating the request for cross-domain file transfer from other requests and centrally processing file transfer through the file processing microservice server, the file processing speed and response speed can be improved. Furthermore, this method is applicable to browsers that do not support cross-domain protocols.

[0064] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described cross-domain file request method.

[0065] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned cross-domain file request method.

[0066] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned cross-domain file request method.

[0067] In this embodiment of the invention, after receiving a file request from a user requesting cross-domain file transfer via a browser's front-end page, the system checks whether the browser supports cross-domain protocols. If the browser supports cross-domain protocols, the file request is sent to a first server connected to a file processing microservice server. The first server accesses the file processing microservice server, enabling it to process the file request. Both the first server and the file processing microservice server are not from the same origin as the front-end page, and the first server supports cross-domain protocols. If the browser does not support cross-domain protocols, the file request is sent to a second server from the same origin as the front-end page. The second server is connected to multiple microservice servers, including the file processing microservice server. The second server can access the file processing microservice server through a reverse proxy, enabling it to process the file request. Compared to existing technical solutions, by separating the request for cross-domain file transfer from other requests and centrally processing file transfer through the file processing microservice server, the file processing speed and response speed can be improved. Furthermore, this method is applicable to browsers that do not support cross-domain protocols.

[0068] The acquisition, storage, use, and processing of data in this application comply with the relevant provisions of national laws and regulations. All types of data, including personal identity data, operational data, and behavioral data related to individuals, customers, and groups, obtained in this application have been authorized.

[0069] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0070] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0071] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0072] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0073] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for cross-domain file requests, characterized in that, include: Receive file requests from users via the browser's front-end page to transfer cross-domain files; Check whether the browser supports cross-domain protocols; If the browser supports the cross-domain protocol, the file request is sent to the first server; wherein the first server is not from the same origin as the front-end page and supports the cross-domain protocol; the first server is connected to the file processing microservice server and is used to access the file processing microservice server so that the file processing microservice server processes the file request; the file processing microservice server is not from the same origin as the front-end page. If the browser does not support the cross-domain protocol, the file request is sent to the second server, wherein the second server is from the same origin as the front-end page, the second server is connected to multiple microservice servers, the multiple microservice servers include the file processing microservice server, and the second server is used to access the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file request; File service requests are decoupled from web service requests, and file requests are processed by a separate file processing microservice server.

2. The method as described in claim 1, characterized in that, The process of receiving a user's request to transfer a cross-domain file via a browser's front-end page includes: Based on the user's actions on the front-end page, parse the business services required by the actions; If the business service includes a file transfer service, the file request is generated.

3. The method as described in claim 1, characterized in that, Before receiving a file request from a user via a browser's front-end page to transfer cross-domain files, it also includes: Add the first server to the whitelist of access addresses of the file processing microservice server.

4. A cross-domain file request device, characterized in that, include: The receiving unit is used to receive file requests from users through the browser's front-end page to transmit cross-domain files; The detection unit is used to detect whether the browser supports cross-domain protocols; A first sending unit is configured to send the file request to a first server when the browser supports the cross-domain protocol; wherein the first server is not from the same origin as the front-end page and supports the cross-domain protocol; the first server is connected to a file processing microservice server and is configured to access the file processing microservice server so that the file processing microservice server processes the file request; the file processing microservice server is not from the same origin as the front-end page; The second sending unit is configured to send the file request to the second server when the browser does not support the cross-domain protocol. The second server is from the same origin as the front-end page and is connected to multiple microservice servers, including the file processing microservice server. The second server is configured to access the file processing microservice server through a reverse proxy so that the file processing microservice server can process the file request. File service requests are decoupled from web service requests, and file requests are processed by a separate file processing microservice server.

5. A business service system, characterized in that, include: Multiple microservice servers, each of which provides a corresponding microservice; The plurality of microservice servers include a file processing microservice server; The first server is connected to the file processing microservice server and is used to receive file requests sent by browsers that support cross-domain protocols, and in response to the file requests, access the file processing microservice server so that the file processing microservice server can process the file requests. The file request is a request from the user to transfer a cross-domain file through the browser's front-end page; The first server and the file processing microservice server are not from the same origin as the front-end page; The second server, connected to the plurality of microservice servers, is used to receive file requests sent by browsers that do not support the cross-domain protocol, and in response to the file request, access the file processing microservice server through a reverse proxy so that the file processing microservice server processes the file request. The second server and the front-end page are from the same origin; File service requests are decoupled from web service requests, and file requests are processed by a separate file processing microservice server.

6. The system as described in claim 5, characterized in that, The first server is an Apache server.

7. The system as described in claim 5, characterized in that, The second server is a website web server.

8. The system as described in claim 5, characterized in that, The file processing microservice server is a JBoss server cluster.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 3.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 3.

11. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 3.

Images