CN113326079A

CN113326079A - Service version switching method, switching device, electronic equipment and storage medium

Info

Publication number: CN113326079A
Application number: CN202110707029.3A
Authority: CN
Inventors: 尤海洋
Original assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Current assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Priority date: 2021-06-24
Filing date: 2021-06-24
Publication date: 2021-08-31

Abstract

The disclosure provides a service version switching method which can be applied to the financial field and the big data technical field. The service version switching method comprises the following steps: acquiring a version switching request, wherein the version switching request comprises target version identification information, and the target version identification information corresponds to a target version identification; in response to the version switching request, determining a target resource list associated with the target version identification from the service version table; acquiring target resource files corresponding to each target resource file identifier according to the target resource file identifiers in the target resource list; and processing the target resource file to complete the service version switching. The present disclosure also provides a service version switching apparatus, device, storage medium, and program product.

Description

Service version switching method, switching device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of finance and big data technology, and more particularly, to a service version switching method, apparatus, device, medium, and program product.

Background

Products such as service systems, applications and software generally include a plurality of versions, and version updating is performed on the products some time after the products are released, and version switching is required during version updating. In the related art, a plurality of servers are arranged, each server stores one version, and version switching is completed in a mode of opening and closing the servers.

In implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: in the related art, a plurality of servers are required to complete switching of product versions, which causes waste of server resources.

Disclosure of Invention

In view of the above, the present disclosure provides a service version switching method, apparatus, device, medium, and program product.

According to a first aspect of the present disclosure, there is provided a service version switching method, including:

acquiring a version switching request, wherein the version switching request comprises target version identification information, and the target version identification information corresponds to a target version identification;

in response to the version switching request, determining a target resource list associated with the target version identification from a service version table, wherein the service version table comprises version identifications corresponding to each service version and a resource list, the resource list comprises at least one resource file identification corresponding to the service version, and each resource file identification corresponds to one resource file;

acquiring a target resource file corresponding to each target resource file identifier according to the target resource file identifier in the target resource list;

and processing the target resource file to complete service version switching.

According to the embodiment of the present disclosure, the service version switching method further includes:

uploading the resource files associated with each of the service versions to a target storage system;

wherein, according to the target resource file identifier in the target resource list, acquiring the target resource file corresponding to each target resource file identifier comprises:

determining the position information of the target resource file in the target storage system according to the target resource file identifier in the target resource list;

and acquiring the target resource file according to the position information.

and sequencing the version identification corresponding to each service version in the target storage system according to the uploading time to generate a service version sequence list.

determining the number of the version identifications in the service version sequence table;

and deleting the resource file associated with the version identifier with the highest priority in the service version sequence list under the condition that the number is greater than a preset threshold value.

deleting the resource file associated with the service version before the version switch after the service version switch is completed.

acquiring version switching operation, wherein the version switching operation comprises selection operation of the target version identifier;

generating the version switch request in response to the version switch operation.

According to an embodiment of the present disclosure, the processing the target resource file to complete the service version switching includes:

and replacing the resource file corresponding to the service version before the version switching with the target resource file to finish the service version switching.

According to an embodiment of the present disclosure, the resource files include a program file, a cascading style sheet file, a hypertext markup language file, and a picture file.

A second aspect of the present disclosure provides a service version switching apparatus, including:

the system comprises a first obtaining module, a second obtaining module and a third obtaining module, wherein the first obtaining module is used for obtaining a version switching request, the version switching request comprises target version identification information, and the target version identification information corresponds to a target version identification;

a first determining module, configured to determine, in response to the version switching request, a target resource manifest associated with the target version identifier from a service version table, where the service version table includes a version identifier and a resource manifest corresponding to each service version, the resource manifest includes at least one resource file identifier corresponding to the service version, and each resource file identifier corresponds to one resource file;

the second acquisition module is used for acquiring a target resource file corresponding to each target resource file identifier according to the target resource file identifier in the target resource list;

and the processing module is used for processing the target resource file so as to complete the service version switching.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the service version switching method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the service version switching method described above.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the service version switching method described above.

According to the embodiment of the disclosure, a target resource list corresponding to a target version identification is determined by acquiring the target version identification in the version switching request, a target file is acquired according to the target resource list, and finally the version switching of a product is completed according to the target resource file. Because the target resource file is acquired after the version resource file is received, the version switching work of the product can be completed only by replacing the resource file by one server when the version is switched, and the technical effect of saving server resources is achieved. The technical problem of server resource waste caused by the fact that the product version switching is completed through a plurality of servers in the related art is at least partially solved.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

fig. 1 schematically shows an application scenario diagram of a service version switching method according to an embodiment of the present disclosure.

Fig. 2 schematically shows a flowchart of a service version switching method according to an embodiment of the present disclosure.

FIG. 3 schematically shows a schematic diagram of a selection page of a target version identification according to an embodiment of the present disclosure.

Fig. 4 schematically shows a version switching method according to an embodiment of the present disclosure.

Fig. 5 schematically shows a block diagram of a service version switching apparatus according to an embodiment of the present disclosure.

Fig. 6 schematically shows a block diagram of an electronic device adapted to implement a version switching method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

After products such as service systems, applications and software are put into use, the change requirements are put forward after a period of time operation, and great correction or error correction is needed to be carried out, so that the functions are enhanced or the performance is improved. In the related version switching method, generally, resource files of different versions are distributed to a plurality of servers, and when a certain version is online, a server corresponding to the version is started, and servers corresponding to other versions are closed.

However, in the course of implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: in the related art, a plurality of servers are required to complete switching of product versions, which causes waste of server resources.

The embodiment of the disclosure provides a service version method and a device, wherein the method comprises the following steps: acquiring a version switching request, wherein the version switching request comprises target version identification information, and the target version identification information corresponds to a target version identification; responding to the version switching request, and determining a target resource list associated with a target version identification from a service version table, wherein the service version table comprises a version identification and a resource list corresponding to each service version, the resource list comprises at least one resource file identification corresponding to the service version, and each resource file identification corresponds to one resource file; acquiring target resource files corresponding to each target resource file identifier according to the target resource file identifiers in the target resource list; and processing the target resource file to complete the service version switching.

It should be noted that the method and the device for switching the service version in the embodiments of the present disclosure may be used in the financial field and the field of big data technology, and may also be used in other technical fields except the financial field and the field of big data technology.

As shown in fig. 1, the application scenario 100 according to this embodiment may include a network, a terminal device, and a server. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the service version switching method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the service version switching device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The service version switching method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the service version switching device provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The service version switching method of the disclosed embodiment will be described in detail below with fig. 2 to 4 based on the scenario described in fig. 1.

As shown in fig. 2, the service version switching method of this embodiment includes operations S201 to S204, and may be performed by a terminal device or a server.

In operation S201, a version switching request is obtained, where the version switching request includes target version identification information, and the target version identification information corresponds to a target version identification.

According to an embodiment of the present disclosure, the version identifier may include, for example, a text identifier, a symbol identifier, a picture identifier, or a color identifier. The textual identification may include, for example, a first version, a second version, a third version, and so on. The symbol identifiers may include, for example, V1.0, V1.1, V2.0, and so on. The picture identification may for example comprise an identification of the picture with the respective version number. The color identification may include, for example, an identification representing the respective versions by different colors, or the like.

According to the embodiment of the disclosure, the target version identification information corresponds to the version identification one to one. Since the system cannot directly recognize and process the version identifier, the version identifier needs to be processed so that the version identifier becomes version identifier information that can be recognized by the system.

It should be noted that the foregoing embodiments are only exemplary embodiments, and the version identifier may be in any other form according to specific implementation needs.

In operation S202, in response to the version switching request, a target resource manifest associated with a target version identifier is determined from a service version table, where the service version table includes a version identifier corresponding to each service version and a resource manifest, the resource manifest includes at least one resource file identifier corresponding to the service version, and each resource file identifier corresponds to one resource file.

According to embodiments of the present disclosure, the resource file may comprise, for example, a static resource file of a service version. Static resource files may include, for example, javascript files, css (cascading style sheet) files, html (hypertext markup language) files, picture files, and the like. Each resource manifest may, for example, include resource file identifications for all resource files corresponding to its service version. The resource file identification may include, for example, a name identification, an identifier identification, etc. of the resource file. Further, the resource file identifier may further include, for example, storage location information of each static resource file thereof, so that the system can determine the storage location of each static resource file according to the resource file identifier.

According to the embodiment of the disclosure, the method for determining the target resource list associated with the target version identification from the service version table comprises the following steps: and determining target version identification information in the version switching request, and determining the target version identification needing to be switched according to the target version identification information. And determining a target resource list associated with the target version identification in the server version according to the target version identification.

According to embodiments of the present disclosure, the service version table may be continuously updated, for example, according to the continuous development of product versions. For example, a newly developed product initially has two versions, which may include, for example, a first version and an alternate version. And after the product development is finished, matching the version identifications of the two versions with the resource list, and filling the version identifications into a service version table.

In the subsequent development process, the version identification and the resource list of the new version can be updated to the service version table so as to facilitate the switching use of the subsequent version.

In operation S203, a target resource file corresponding to each target resource file identifier is obtained according to the target resource file identifier in the target resource list.

According to an embodiment of the present disclosure, the target resource file identification may include, for example, storage location information of the target resource file or storage location information associated with the target resource file. The system may determine, based on the target resource file identifier, a storage location of the target resource file corresponding to the target resource file identifier. And acquiring all target resource files according to the storage position.

In operation S204, the target resource file is processed to complete the service version switching.

According to an embodiment of the present disclosure, the method for processing the target resource file may include, for example, replacing the current resource file with the target resource file. The current resource file may refer to, for example, a resource file used by the current version of the product, etc.

According to the embodiment of the present disclosure, the service version switching method further includes: the resource files associated with each service version are uploaded to the target storage system.

According to an embodiment of the present disclosure, the target storage system may include, for example, a cloud storage system. The cloud storage system may include, for example, OSS object storage, cloud disks, mesh disks, and so forth.

According to the embodiment of the present disclosure, acquiring a target resource file corresponding to each target resource file identifier according to the target resource file identifier in the target resource list includes:

determining the position information of the target resource file in the target storage system according to the target resource file identification in the target resource list; and acquiring the target resource file according to the position information.

According to an embodiment of the present disclosure, the target resource file identification may include, for example, storage location information of the target resource file or storage location information associated with the target resource file. Specifically, the target resource file identifier may have, for example, storage location information of the target resource file. Or, the target resource file identifier is associated with another storage file, and the storage file stores the storage location information of the target resource file. The system may determine, based on the target resource file identifier, a storage location of the target resource file corresponding to the target resource file identifier. And acquiring all target resource files according to the storage position.

According to the embodiment of the disclosure, the resource file is stored in the cloud storage system, so that the storage pressure of the server can be relieved. When the version needs to be switched, the target resource file in the cloud storage system is downloaded to the server, and then the resource file can be replaced, so that the version switching function is realized. Therefore, when multi-version resources coexist, only one server is needed to meet the function of multi-version switching without additionally increasing server storage resource files. In addition, the server for switching versions does not need to store resource files in a plurality of versions, so that the destruction, addition and other operations of the server do not influence the resource files.

Furthermore, because the version switching is completed on the same server, the operation of starting and closing a plurality of servers in sequence is not needed, so that the speed of the version switching can be improved, and the product service does not need to be stopped in the version switching process.

According to an embodiment of the present disclosure, multiple versions of a resource file may exist in a target storage system. To facilitate management of the resource files in the target storage system, for example, the resource files may be sorted according to the uploading time or version number of the resource file corresponding to each version identifier, and a service version sequence table may be generated.

determining the number of the version identifications in the service version sequence table; and deleting the resource file associated with the version identifier with the highest priority in the service version sequence list under the condition that the number of the resource files is larger than the preset threshold.

According to the embodiment of the present disclosure, for example, a target number threshold of the version identifier may be preset, and when the number of the version resource files in the target storage system is large, the number of the version identifier may exceed the target number threshold. At this time, the resource file of the version with longer uploading time can be deleted, so as to save the storage resource of the storage system. Specifically, the resource file to be deleted can be determined in a manual selection mode, so that the use requirement of a developer is met.

According to an embodiment of the present disclosure, the version switching method further includes:

after the service version switch is completed, the resource file associated with the service version before the version switch is deleted.

According to the embodiment of the disclosure, after the resource file is replaced by the target resource file, the resource file associated with the service version before the version switching can be deleted in the server, so as to free up the storage space of the server.

acquiring version switching operation, wherein the version switching operation comprises selection operation of a target version identifier; in response to the version switch operation, a version switch request is generated.

According to an embodiment of the present disclosure, the selection operation of the target version identification may be performed, for example, on a carrier. The carrier may for example comprise an electronic device, the electronic device may comprise a terminal device, the terminal device may comprise a smartphone, a tablet, a portable computer or a desktop computer or the like. The selection operation may include a click or a slide.

As shown in fig. 3, the page includes at least a product name presentation area 301, a service version selection area 302, and a determination area 303. The name presentation area 301 may include, for example, the name of the product and current version information. The service version selection area 302 may include, for example, an identification of versions stored in the target storage system. The determination area 303 may include, for example, a switch button or the like.

Specifically, the user may determine the name and version information of the product corresponding to the current page through the name display area 301. By selecting the version id of the target version in the service version selection area 302, and finally clicking the switch button, the version switching operation can be completed.

According to an embodiment of the present disclosure, processing the target resource file to complete the service version switching includes: and replacing the resource file corresponding to the service version before the version switching with the target resource file to complete the service version switching.

As shown in fig. 4, this approach may be performed, for example, by a client 401, a server 402, a storage system 403, and a development system 404.

The development system 404 is controlled by the developer who can upload resource files to the storage system 403 through the development system 404 after developing a version of a product. The developer may then select the version through the development system 404, and the server 402 receives the version switching instruction of the development system 404 and downloads the resource file to the server 402 in the storage system 403. After processing the resource file, the client 401 receives the processed file and generates a final product.

During subsequent development, the developer may upload each version of the resource file to the storage system 403. When version switching is required, the server 402 can download a required resource file in the storage system 403 by selecting a target version identifier on the development system 404, and complete replacement of the resource file. Finally, switching of product versions is achieved at the client 401.

Based on the service version switching method, the embodiment of the disclosure also provides a service version switching device. The apparatus will be described in detail below with reference to fig. 5.

As shown in fig. 5, the service version switching apparatus 500 of this embodiment includes a first obtaining module 501, a first determining module 502, a second obtaining module 503, and a processing module 504.

The first obtaining module 501 is configured to obtain a version switching request, where the version switching request includes target version identification information, and the target version identification information corresponds to a target version identification. In an embodiment, the first obtaining module 501 may be configured to perform the operation S201 described above, which is not described herein again.

A first determining module 502, configured to determine, in response to the version switching request, a target resource manifest associated with a target version identifier from a service version table, where the service version table includes a version identifier corresponding to each service version and a resource manifest, and the resource manifest includes at least one resource file identifier corresponding to the service version, and each resource file identifier corresponds to one resource file. In an embodiment, the determining module may be configured to perform the operation S202 described above, which is not described herein again.

A second obtaining module 503, configured to obtain, according to the target resource file identifier in the target resource list, a target resource file corresponding to each target resource file identifier. In an embodiment, the second obtaining module 503 may be configured to perform the operation S203 described above, which is not described herein again.

The processing module 504 is configured to process the target resource file to complete service version switching. In an embodiment, the processing module 504 may be configured to perform the operation S204 described above, which is not described herein again.

According to an embodiment of the present disclosure, the service version switching apparatus 500 further includes an uploading module.

And the uploading module is used for uploading the resource file associated with each service version to the target storage system.

The second obtaining module 503 includes a determining unit and a obtaining unit.

And the determining unit is used for determining the position information of the target resource file in the target storage system according to the target resource file identifier in the target resource list.

And the acquisition unit is used for acquiring the target resource file according to the position information.

According to an embodiment of the present disclosure, the service version switching apparatus 500 further includes a sorting module.

And the sequencing module is used for sequencing the version identification corresponding to each service version in the target storage system according to the uploading time to generate a service version sequence list.

According to an embodiment of the present disclosure, the service version switching apparatus 500 further includes a second determining module and a first deleting module.

And the second determining module is used for determining the number of the version identifications in the service version sequence table.

And the first deleting module is used for deleting the resource file associated with the version identifier with the highest priority in the service version sequence list under the condition that the number of the resource files is larger than a preset threshold value.

According to an embodiment of the present disclosure, the service version switching apparatus 500 further includes a second deleting module.

And the second deleting module is used for deleting the resource file associated with the service version before the version switching after the service version switching is finished.

According to the embodiment of the present disclosure, the service version switching apparatus 500 further includes a third obtaining module and a response module.

And the third obtaining module is used for obtaining the version switching operation, wherein the version switching operation comprises the selection operation of the target version identifier.

And the response module is used for responding to the version switching operation and generating a version switching request.

According to an embodiment of the present disclosure, the processing module 504 includes a replacement unit.

And the replacing unit is used for replacing the resource file corresponding to the service version before the version switching with the target resource file so as to complete the service version switching.

According to the embodiment of the present disclosure, any plurality of the first obtaining module 501, the first determining module 502, the second obtaining module 503, and the processing module 504 may be combined and implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first obtaining module 501, the first determining module 502, the second obtaining module 503 and the processing module 504 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented by any one of three implementations of software, hardware and firmware, or any suitable combination of any of them. Alternatively, at least one of the first obtaining module 501, the first determining module 502, the second obtaining module 503 and the processing module 504 may be at least partly implemented as a computer program module, which when executed may perform a corresponding function.

As shown in fig. 6, an electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. Processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 601 may also include onboard memory for caching purposes. Processor 601 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.

In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 602 and/or RAM 603. It is to be noted that the programs may also be stored in one or more memories other than the ROM 602 and RAM 603. The processor 601 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 600 may also include input/output (I/O) interface 605, input/output (I/O) interface 605 also connected to bus 604, according to an embodiment of the disclosure. The electronic device 600 may also include one or more of the following components connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 602 and/or RAM 603 described above and/or one or more memories other than the ROM 602 and RAM 603.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the item recommendation method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 601. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 609, and/or installed from the removable medium 611. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program, when executed by the processor 601, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A service version switching method comprises the following steps:

and processing the target resource file to complete service version switching.

2. The method of claim 1, further comprising:

and acquiring the target resource file according to the position information.

3. The method of claim 2, further comprising:

4. The method of claim 3, further comprising:

5. The method of claim 1, further comprising:

6. The method of claim 1, further comprising:

7. The method of claim 1, wherein the processing the target resource file to complete a service version switch comprises:

8. The method of claim 1, wherein the resource files include program files, cascading style sheet files, hypertext markup language files, and picture files.

9. A service version switching apparatus comprising:

10. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 8.

12. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 8.