Application program publishing method and device, storage medium, program and electronic equipment

Abstract

The invention provides an application program publishing method and device, a storage medium, a program and electronic equipment, and the method comprises the steps: receiving to-be-loaded function plug-in information of an application program, the to-be-loaded function plug-in information at least comprising a target version number and a target plug-in name; determining at least one piece of target application plug-in information and a target plug-in slot from a plurality of pieces of application plug-in information in a user plug-in version library according to the target plug-in name; under the condition that the target version number is higher than the version number of each piece of target application plug-in information, sending the to-be-loaded function plug-in information to a target plug-in slot through an open interface; and loading and running the to-be-loaded functional plug-in information through the target plug-in slot to update the functional plug-in in the target plug-in slot. According to the method, the high-version to-be-loaded function plug-in information is sent to the target plug-in slot through the open interface, mutual registration between systems is not involved, the whole application does not need to be redeployed, and the publishing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of software development and deployment, and in particular, to a method for publishing an application, a publishing device, a computer-readable storage medium, a computer program product, and an electronic device. Background Art

[0002] Traditional application releases often require the redeployment of the entire application, and because the release process involves multiple systems, systems need to register with each other, resulting in low release efficiency. Summary of the invention

[0003] The main purpose of the present application is to provide a method for publishing an application, a publishing device, a computer-readable storage medium, a computer program product and an electronic device, so as to at least solve the problem in the prior art that systems need to register with each other and the publishing efficiency is low.

[0004] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for publishing an application is provided, comprising: receiving function plug-in information to be loaded of the application, the function plug-in information to be loaded at least comprising a target version number and a target plug-in name, the target version number being the version number of the function plug-in to be loaded, and the target plug-in name being the plug-in name of the function plug-in to be loaded; according to the target plug-in name, determining at least one target application plug-in information from multiple application plug-in information in a user plug-in version library, and determining a target plug-in slot, the target application plug-in information being the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, the application plug-in information comprising the application The plug-in name and version number corresponding to the plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a functional plug-in to implement the function of the functional plug-in, and the open interface is used to provide a standard way to access the plug-in slot; when the target version number is higher than the version number of each target application plug-in information, the open interface is called to send the to-be-loaded functional plug-in information to the target plug-in slot through the open interface; the to-be-loaded functional plug-in information is loaded and run through the target plug-in slot to update the functional plug-in in the target plug-in slot.

[0005] Optionally, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0006] Optionally, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0007] Optionally, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, the integrity detection at least including detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0008] Optionally, after receiving the to-be-loaded function plug-in information of the application, the method further comprises: storing the to-be-loaded function plug-in information in a to-be-loaded plug-in directory.

[0009] Optionally, the method further includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0010] According to another aspect of the present application, a publishing device for an application is provided, comprising: a receiving unit, configured to receive information of a function plug-in to be loaded of the application, the function plug-in information to be loaded at least comprising a target version number and a target plug-in name, the target version number being the version number of the function plug-in to be loaded, and the target plug-in name being the plug-in name of the function plug-in to be loaded; a determining unit, configured to determine at least one target application plug-in information from a plurality of application plug-in information in a user plug-in version library according to the target plug-in name, and to determine a target plug-in slot, the target application plug-in information being the application plug-in information corresponding to the plug-in name identical to the target plug-in name, the application plug-in information comprising the application plug-in corresponding to the target plug-in name; The plug-in name and version number, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a functional plug-in to implement the function of the functional plug-in, and the open interface is used to provide a standard way to access the plug-in slot; a calling unit is used to call the open interface when the target version number is higher than the version number of each target application plug-in information, and send the to-be-loaded functional plug-in information to the target plug-in slot through the open interface; a loading unit is used to load and run the to-be-loaded functional plug-in information through the target plug-in slot to update the functional plug-in in the target plug-in slot.

[0011] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the methods described.

[0012] According to another aspect of the present application, a computer program product is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, any one of the methods described above is implemented.

[0013] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of the methods described.

[0014] By applying the technical solution of the present application, firstly, the function plug-in information to be loaded of the application is received, the function plug-in information to be loaded includes at least a target version number and a target plug-in name, the target version number is the version number of the function plug-in to be loaded, the target plug-in name is the plug-in name of the function plug-in to be loaded, and then according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version corresponding to the application plug-in The target plug-in slot is one of the multiple plug-in slots, and the plug-in slot is used to load the functional plug-in to realize the function of the functional plug-in. The open interface is used to provide a standard way to access the plug-in slot. Then, when the target version number is higher than the version number of each target application plug-in information, the open interface is called to send the functional plug-in information to be loaded to the target plug-in slot through the open interface, and finally the functional plug-in information to be loaded is loaded and run through the target plug-in slot to update the functional plug-in in the target plug-in slot. This application sends the functional plug-in information to be loaded to the target plug-in slot by calling the open interface on the application base, so the push of functional plug-in information can be realized without mutual registration. The application is developed based on the application base, and the application base includes multiple plug-in slots. The functional plug-in of the application can be updated by loading the high-version functional plug-in information into the target plug-in slot, without the need to redeploy the entire application, thereby improving the publishing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 A hardware structure block diagram of a mobile terminal for executing a method for publishing an application program provided in an embodiment of the present application is shown;

[0017] Figure 2 A schematic diagram of a process of publishing an application program provided according to an embodiment of the present application is shown;

[0018] Figure 3 A flowchart of a method for publishing an application program provided according to an embodiment of the present application is shown;

[0019] Figure 4A schematic diagram of a method for publishing an application program provided according to an embodiment of the present application is shown;

[0020] Figure 5 A structural block diagram of a device for publishing an application program provided according to an embodiment of the present application is shown.

[0021] The above drawings include the following reference numerals:

[0022] 102. Processor; 104. Memory; 106. Transmission device; 108. Input and output device; 10. Version service; 12. Application; 14. Application base; 16. Plug-in operating environment; 18. Plug-in slot; 20. Functional plug-in. DETAILED DESCRIPTION

[0023] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the accompanying drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] As introduced in the background technology, in the prior art, systems need to register with each other, and the publishing efficiency is low. To solve the above technical problems, the embodiments of the present application provide an application publishing method, a publishing device, a computer-readable storage medium, a computer program product, and an electronic device.

[0027] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0028] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 FIG. 1 is a hardware structure diagram of a mobile terminal of a method for publishing an application program according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the mobile terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0029] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the publishing method of the application program in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the method described is implemented. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile terminal via a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. The transmission device 106 is used to receive or send data via a network. The specific example of the network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0030] In this embodiment, a method for publishing an application running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0031] Figure 2 FIG. 1 is a flow chart of a method for publishing an application according to an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:

[0032] Step S201, receiving information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0033] Step S202: according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0034] Step S203, when the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface;

[0035] Step S204: Load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0036] According to the embodiment, first, the function plug-in information to be loaded of the application is received, the function plug-in information to be loaded includes at least a target version number and a target plug-in name, the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded, then according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, the open interface is used to provide a standard way to access the plug-in slot, then when the target version number is higher than the version number of each target application plug-in information, the open interface is called, the function plug-in information to be loaded is sent to the target plug-in slot through the open interface, and finally the function plug-in information to be loaded is loaded and run through the target plug-in slot to update the function plug-in in the target plug-in slot. This application sends the function plug-in information to be loaded to the target plug-in slot by calling the open interface on the application base, so the function plug-in information can be pushed without mutual registration. The application is developed based on the application base, and the application base contains multiple plug-in slots. The function plug-in of the application can be updated by loading the higher version of the function plug-in information into the target plug-in slot, without redeploying the entire application, thereby improving the publishing efficiency.

[0037] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0038] In an optional scheme, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0039] In the embodiment, different applications correspond to different application bases. Through the target application identifier, it is possible to accurately identify for which application the function plug-in to be loaded is designed, thereby ensuring the matching between the plug-in and the application. After identifying the target application, the corresponding target application base is further determined based on the application. The application base is the basic framework for the operation of the application, which supports the loading and operation of plug-ins. Then, based on the name of the function plug-in to be loaded, the target plug-in slot is determined from multiple plug-in slots corresponding to the target application base, thereby ensuring that the plug-in can be correctly loaded.

[0040] In some other exemplary embodiments, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0041] In the embodiment, the business content of the application is split so that there is no dependency between any two split business contents, so that each business module can operate independently without interfering with each other. Therefore, when updating a plug-in, there is no need to redeploy the entire application, only the plug-in that needs to be updated needs to be replaced, which improves the publishing efficiency.

[0042] Specifically, functional plug-ins represent different business functions and can be configuration files, functional codes, etc. They have the ability to be loaded into plug-in slots after being packaged according to plug-in requirements.

[0043] In another optional scheme, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, and the integrity detection at least includes detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0044] In the embodiment, the function plug-in information to be loaded is stored in the user plug-in version library, so as to facilitate the subsequent retrieval of the plug-in information to be used from the library. The integrity of the function plug-in information to be loaded stored in the version library is checked to ensure that the function plug-in information is not damaged or lost during the transmission and storage process, thereby ensuring the normal operation of the function plug-in.

[0045] Specifically, before updating, the compatibility and correctness of the function plug-in to be loaded may be further verified. For example, it may be checked whether the function plug-in to be loaded matches the interface specification of the target plug-in slot and whether it meets the security requirements and performance standards of the system.

[0046] Specifically, integrity detection can be implemented by comparing file sizes, checking and / or other checking mechanisms. These mechanisms can ensure that every byte of the file is consistent with the original file, thereby preventing data tampering or damage.

[0047] In another optional solution, after receiving the information of the function plug-in to be loaded of the application, the method further includes: storing the information of the function plug-in to be loaded in a plug-in directory to be loaded.

[0048] In the embodiment, creating a directory of plug-ins to be loaded helps to manage information of functional plug-ins to be loaded.

[0049] In some other exemplary schemes of the present application, the method also includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving the executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0050] In the embodiment, the entire process from detecting an abnormality or error in the operation of a functional plug-in to replacing the plug-in is automated without manual intervention, thereby improving the response speed of the system and also improving the stability of the system.

[0051] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the data storage method of the present application will be described in detail below in conjunction with specific embodiments.

[0052] This embodiment relates to a specific method for publishing an application program, such as Figure 3 As shown, the following steps are included:

[0053] Step S1: receiving information of function plug-in to be loaded;

[0054] Step S2: Push the function plug-in information to be loaded;

[0055] Step S3: storing the information of the function plug-in to be loaded into the plug-in directory to be loaded;

[0056] Step S4: Send the function plug-in information to be loaded to the target plug-in slot;

[0057] Step S5: The target plug-in slot loads and runs the function plug-in information to be loaded.

[0058] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0059] Figure 4 The implementation method of the present invention is shown by way of example. The application base 14 is a lightweight custom program used to build the application 12, which includes three parts: a plug-in operating environment 16, a plug-in slot 18, and a functional plug-in 20. The plug-in operating environment 16 is a custom main program of the application base 14, which provides services to the outside, receives plug-in push requests and control commands from the version service 10, and is saved by the functional plug-in 20. The plug-in slot 18 is loaded through the JVM bytecode loading mechanism after receiving the delivery of the functional plug-in 20 from the plug-in operating environment 16, and controls the running state of the functional plug-in 20. The functional plug-in 20 is a custom subroutine of the application base 14, which is a loadable functional component written and packaged according to the development specification of the functional plug-in 20, and is called a functional plug-in 20. Different functional plug-ins 20 are isolated from each other, and are combined to complete the business functions of the application 12. The application 12 is built on the application base 14, composed of functional plug-ins 20 with different functions, has real business meaning, and can provide business services to the outside. The version service 10 is a lightweight custom program that controls the life cycle, push time, and release scope of the functional plug-in 20. The application 12 is built based on the application base 14, contains a variety of functional plug-ins 20, and is the object of application release. The version service 10 is mainly responsible for the function and status control of the functional plug-in 20, and cooperates with the application 12 to complete the application release function. The plug-in operating environment 16 provides the operating environment of the plug-in slot 18, so that the plug-in slot 18 has the ability to automatically load and update business plug-ins; the plug-in operating environment 16 provides service opening capabilities and opens the operation interface to the outside world, so that the external application 12 can remotely control the application base 14. The plug-in slot 18 provides a function plug-in 20 running container, which can isolate the function plug-ins 20 of different functions, and adjust the number of plug-in slots 18 according to the number of plug-ins in the user plug-in version library. The version service 10 mainly performs unified control on the versions of the function plug-ins 20 of different functions, making the release process more standardized and normative; by remotely calling the operation interface opened by the plug-in operating environment 16, the functions of the actual application 12 are finely controlled.

[0060] The embodiment of the present application also provides a publishing device for an application. It should be noted that the publishing device for the application in the embodiment of the present application can be used to execute the publishing method for the application provided in the embodiment of the present application. The device is used to implement the embodiments and preferred implementations, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0061] The following is an introduction to the application publishing device provided in the embodiment of the present application.

[0062] Figure 5 Schematic diagram of a publishing device for an application according to an embodiment of the present application. Figure 5 As shown, the device comprises:

[0063] The receiving unit 30 is used to receive information about a function plug-in to be loaded of an application program, wherein the information about the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0064] a determining unit 40, configured to determine at least one target application plug-in information from a plurality of application plug-in information in a user plug-in version library according to the target plug-in name, and to determine a target plug-in slot, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes a plurality of plug-in slots and an open interface, the target plug-in slot is one of the plurality of plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0065] A calling unit 50 is used to call the open interface and send the function plug-in information to be loaded to the target plug-in slot through the open interface when the target version number is higher than the version number of each target application plug-in information;

[0066] The loading unit 60 is used to load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0067] According to the embodiment, a receiving unit receives function plug-in information to be loaded of an application program, the function plug-in information to be loaded includes at least a target version number and a target plug-in name, the target version number is the version number of the function plug-in to be loaded, the target plug-in name is the plug-in name of the function plug-in to be loaded, and a determining unit determines at least one target application plug-in information from a plurality of application plug-in information in a user plug-in version library according to the target plug-in name, and determines a target plug-in slot, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in , the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a functional plug-in to implement the function of the functional plug-in, and the open interface is used to provide a standard way to access the plug-in slot. When the target version number is higher than the version number of each target application plug-in information, the calling unit calls the open interface, sends the functional plug-in information to be loaded to the target plug-in slot through the open interface, and loads and runs the functional plug-in information to be loaded through the target plug-in slot by the loading unit to update the functional plug-in in the target plug-in slot. This application sends the functional plug-in information to be loaded to the target plug-in slot by calling the open interface on the application base, so the push of functional plug-in information can be realized without mutual registration, and the application is developed based on the application base, and the application base includes multiple plug-in slots. The functional plug-in of the application can be updated by loading the high-version functional plug-in information into the target plug-in slot, without the need to redeploy the entire application, thereby improving the publishing efficiency.

[0068] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0069] In another optional solution, the determining unit includes:

[0070] A determination module is used to determine the target application according to the target application identifier, determine the target application base corresponding to the target application according to the target application, and determine the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0071] In the embodiment, different applications correspond to different application bases. Through the target application identifier, it is possible to accurately identify for which application the function plug-in to be loaded is designed, thereby ensuring the matching between the plug-in and the application. After identifying the target application, the corresponding target application base is further determined based on the application. The application base is the basic framework for the operation of the application, which supports the loading and operation of plug-ins. Then, based on the name of the function plug-in to be loaded, the target plug-in slot is determined from multiple plug-in slots corresponding to the target application base, thereby ensuring that the plug-in can be correctly loaded.

[0072] In another optional solution, the device further includes:

[0073] A splitting unit, used for splitting the business content of the application so that there is no dependency between any two split business contents;

[0074] A generating unit, configured to generate a plurality of corresponding functional plug-ins according to the plurality of split business contents;

[0075] a configuration unit, configured to configure the plug-in slots according to the number of the generated functional plug-ins, so that the number of the functional plug-ins is equal to the number of the plug-in slots;

[0076] The loading unit is used to load the plurality of functional plug-ins into each of the plug-in slots in a one-to-one correspondence.

[0077] In the embodiment, the business content of the application is split so that there is no dependency between any two split business contents, so that each business module can operate independently without interfering with each other. Therefore, when updating a plug-in, there is no need to redeploy the entire application, only the plug-in that needs to be updated needs to be replaced, which improves the publishing efficiency.

[0078] Specifically, functional plug-ins represent different business functions and can be configuration files, functional codes, etc. They have the ability to be loaded into plug-in slots after being packaged according to plug-in requirements.

[0079] In another optional solution, the device further includes:

[0080] A first storage unit, used for storing the information of the function plug-in to be loaded into the user plug-in version library;

[0081] A first detection unit, configured to perform integrity detection on the information of the function plug-in to be loaded, wherein the integrity detection at least includes detecting whether the code and configuration file of the function plug-in to be loaded are complete;

[0082] An updating unit is used to update the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded so as to implement the function of the target plug-in when the information of the function plug-in to be loaded is complete, and to send the information of the function plug-in to be loaded to the plug-in slot again through the open interface when the information of the function plug-in to be loaded is incomplete.

[0083] In the embodiment, the function plug-in information to be loaded is stored in the user plug-in version library, so as to facilitate the subsequent retrieval of the plug-in information to be used from the library. The integrity of the function plug-in information to be loaded stored in the version library is checked to ensure that the function plug-in information is not damaged or lost during the transmission and storage process, thereby ensuring the normal operation of the function plug-in.

[0084] Specifically, before updating, the compatibility and correctness of the function plug-in to be loaded may be further verified. For example, it may be checked whether the function plug-in to be loaded matches the interface specification of the target plug-in slot and whether it meets the security requirements and performance standards of the system.

[0085] Specifically, integrity detection can be implemented by comparing file sizes, checking and / or other checking mechanisms. These mechanisms can ensure that every byte of the file is consistent with the original file, thereby preventing data tampering or damage.

[0086] In another optional solution, the device further includes:

[0087] The second storage unit is used to store the information of the function plug-in to be loaded into the plug-in directory to be loaded.

[0088] In the embodiment, creating a directory of plug-ins to be loaded helps to manage information of functional plug-ins to be loaded.

[0089] In some other exemplary embodiments, the device further comprises:

[0090] The second detection unit is used to stop the operation of the updated functional plug-in and retrieve the executable functional plug-in information from the user plug-in version library to replace the functional plug-in when detecting that the updated functional plug-in in the target plug-in slot has an abnormality or error in its operation.

[0091] In the embodiment, the entire process from detecting an abnormality or error in the operation of a functional plug-in to replacing the plug-in is automated without manual intervention, thereby improving the response speed of the system and also improving the stability of the system.

[0092] The application publishing device includes a processor and a memory, wherein the receiving unit, the determining unit, the calling unit, and the loading unit are all stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions. The modules are all located in the same processor; or, the modules are located in different processors in any combination.

[0093] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the problem of low publishing efficiency in the prior art that systems need to register with each other can be solved by adjusting kernel parameters.

[0094] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0095] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, a device where the computer-readable storage medium is located is controlled to execute the method for publishing the application program.

[0096] Specifically, the application publishing methods include:

[0097] Step S201, receiving information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0098] Step S202: according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0099] Step S203, when the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface;

[0100] Step S204: Load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0101] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0102] Optionally, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0103] Optionally, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0104] Optionally, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, the integrity detection at least including detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0105] Optionally, after receiving the to-be-loaded function plug-in information of the application, the method further comprises: storing the to-be-loaded function plug-in information in a to-be-loaded plug-in directory.

[0106] Optionally, the method further includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0107] An embodiment of the present invention provides a processor, which is used to run a program, wherein the program executes the publishing method of the application program when it is running.

[0108] Specifically, the application publishing methods include:

[0109] Step S201, receiving information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0110] Step S202: according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0111] Step S203, when the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface;

[0112] Step S204: Load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0113] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0114] Optionally, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0115] Optionally, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0116] Optionally, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, the integrity detection at least including detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0117] Optionally, after receiving the to-be-loaded function plug-in information of the application, the method further comprises: storing the to-be-loaded function plug-in information in a to-be-loaded plug-in directory.

[0118] Optionally, the method further includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0119] The present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement at least the following method steps:

[0120] Step S201, receiving information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0121] Step S202: according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0122] Step S203, when the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface;

[0123] Step S204: Load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0124] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0125] Optionally, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0126] Optionally, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0127] Optionally, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, the integrity detection at least including detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0128] Optionally, after receiving the to-be-loaded function plug-in information of the application, the method further comprises: storing the to-be-loaded function plug-in information in a to-be-loaded plug-in directory.

[0129] Optionally, the method further includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0130] An embodiment of the present invention provides an electronic device, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs include a method for executing any one of the methods described. When the program is executed, at least the following steps are implemented:

[0131] Step S201, receiving information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded;

[0132] Step S202: according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot;

[0133] Step S203, when the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface;

[0134] Step S204: Load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

[0135] Specifically, the application base is a lightweight custom program built on the Java virtual machine.

[0136] Optionally, the information of the function plug-in to be loaded also includes a target application identifier, and the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: determining the target application according to the target application identifier, determining the target application base corresponding to the target application according to the target application, and determining the target plug-in slot from the plug-in slot corresponding to the target application base according to the target plug-in name.

[0137] Optionally, before receiving the information of the functional plug-ins to be loaded of the application, the method also includes: splitting the business content of the application so that there is no dependency between any two split business contents; generating a corresponding plurality of functional plug-ins based on the plurality of split business contents; configuring the plug-in slots based on the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; and loading the plurality of functional plug-ins into each of the plug-in slots one by one.

[0138] Optionally, after sending the information of the function plug-in to be loaded to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded, the method also includes: storing the information of the function plug-in to be loaded to the user plug-in version library; performing integrity detection on the information of the function plug-in to be loaded, the integrity detection at least including detecting whether the code and configuration file of the function plug-in to be loaded are complete; if the information of the function plug-in to be loaded is complete, updating the function plug-in in the target plug-in slot according to the information of the function plug-in to be loaded to implement the function of the target plug-in; if the information of the function plug-in to be loaded is incomplete, sending the information of the function plug-in to be loaded to the plug-in slot again through the open interface.

[0139] Optionally, after receiving the to-be-loaded function plug-in information of the application, the method further comprises: storing the to-be-loaded function plug-in information in a to-be-loaded plug-in directory.

[0140] Optionally, the method further includes: when it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, stopping the operation of the updated functional plug-in, and retrieving executable functional plug-in information from the user plug-in version library to replace the functional plug-in.

[0141] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0142] Obviously, those skilled in the art should understand that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0143] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0144] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0145] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0146] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0147] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0148] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0149] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0150] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0151] From the above description, it can be seen that the embodiments described in this application achieve the following technical effects:

[0152] 1) The publishing method of the application of the present application first receives the function plug-in information to be loaded of the application, the function plug-in information to be loaded at least includes a target version number and a target plug-in name, the target version number is the version number of the function plug-in to be loaded, the target plug-in name is the plug-in name of the function plug-in to be loaded, and then according to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name corresponding to the application plug-in and version number, the application is developed based on the application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load the function plug-in to implement the function of the function plug-in, the open interface is used to provide a standard way to access the plug-in slot, and then when the target version number is higher than the version number of each target application plug-in information, the open interface is called, the function plug-in information to be loaded is sent to the target plug-in slot through the open interface, and finally the function plug-in information to be loaded is loaded and run through the target plug-in slot to update the function plug-in in the target plug-in slot. This application sends the function plug-in information to be loaded to the target plug-in slot by calling the open interface on the application base, so the function plug-in information can be pushed without mutual registration, and the application is developed based on the application base, the application base includes multiple plug-in slots, and the function plug-in of the application can be updated by loading the high version function plug-in information into the target plug-in slot, without the need to redeploy the entire application, thereby improving the publishing efficiency.

[0153] 2) The publishing device of the application of the present application receives the function plug-in information to be loaded of the application through the receiving unit, the function plug-in information to be loaded includes at least a target version number and a target plug-in name, the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded, and the determination unit determines at least one target application plug-in information from multiple application plug-in information in the user plug-in version library according to the target plug-in name, and determines a target plug-in slot, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name corresponding to the application plug-in and version number, the application is developed based on the application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load the function plug-in to implement the function of the function plug-in, the open interface is used to provide a standard way to access the plug-in slot, and the calling unit calls the open interface when the target version number is higher than the version number of each target application plug-in information, and the function plug-in information to be loaded is sent to the target plug-in slot through the open interface, and the loading unit loads and runs the function plug-in information to be loaded through the target plug-in slot to update the function plug-in in the target plug-in slot. This application sends the function plug-in information to be loaded to the target plug-in slot by calling the open interface on the application base, so the function plug-in information can be pushed without mutual registration, and the application is developed based on the application base, and the application base includes multiple plug-in slots. The function plug-in of the application can be updated by loading the high version of the function plug-in information into the target plug-in slot, without the need to redeploy the entire application, thereby improving the publishing efficiency.

[0154] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for publishing an application, characterized in that: include: Receive information about a function plug-in to be loaded of an application, wherein the information about the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is the version number of the function plug-in to be loaded, and the target plug-in name is the plug-in name of the function plug-in to be loaded; According to the target plug-in name, at least one target application plug-in information is determined from multiple application plug-in information in the user plug-in version library, and a target plug-in slot is determined, the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes multiple plug-in slots and open interfaces, the target plug-in slot is one of the multiple plug-in slots, the plug-in slot is used to load a function plug-in to implement the function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot; In the case where the target version number is higher than the version number of each target application plug-in information, calling the open interface, and sending the function plug-in information to be loaded to the target plug-in slot through the open interface; The function plug-in information to be loaded is loaded and executed through the target plug-in slot to update the function plug-in in the target plug-in slot.

2. The method according to claim 1, characterized in that The information of the function plug-in to be loaded also includes a target application identifier, where the target application identifier is an application identifier corresponding to the function plug-in to be loaded. Determining the target plug-in slot includes: The target application is determined according to the target application identifier, the target application base corresponding to the target application is determined according to the target application, and the target plug-in slot is determined from the plug-in slot corresponding to the target application base according to the target plug-in name.

3. The method according to claim 1, characterized in that Before receiving the information of the function plug-in to be loaded of the application, the method further includes: Splitting the business contents of the application so that there is no dependency between any two of the split business contents; Generate corresponding multiple functional plug-ins according to the multiple split business contents; configuring the plug-in slots according to the number of the generated functional plug-ins so that the number of the functional plug-ins is equal to the number of the plug-in slots; The plurality of functional plug-ins are loaded into each of the plug-in slots in a one-to-one correspondence.

4. The method according to claim 1, characterized in that: After sending the to-be-loaded function plug-in information to the target plug-in slot through the open interface, and before the target plug-in slot updates the function plug-in in the target plug-in slot according to the to-be-loaded function plug-in information, the method further includes: Storing the function plug-in information to be loaded into the user plug-in version library; Performing integrity check on the information of the function plug-in to be loaded, wherein the integrity check at least includes checking whether the code and configuration file of the function plug-in to be loaded are complete; When the information of the function plug-in to be loaded is complete, the function plug-in in the target plug-in slot is updated according to the information of the function plug-in to be loaded to implement the function of the target plug-in. When the information of the function plug-in to be loaded is incomplete, the information of the function plug-in to be loaded is sent to the plug-in slot again through the open interface.

5. The method according to claim 1, characterized in that After receiving the information of the function plug-in to be loaded of the application, the method further includes: The information of the function plug-in to be loaded is stored in the plug-in directory to be loaded.

6. The method according to claim 1, characterized in that The method further comprises: When it is detected that an abnormality or error occurs in the operation of the updated functional plug-in in the target plug-in slot, the operation of the updated functional plug-in is stopped, and functional plug-in information that can be run is retrieved from the user plug-in version library to replace the functional plug-in.

7. A device for publishing an application, characterized in that: include: A receiving unit, configured to receive information of a function plug-in to be loaded of an application, wherein the information of the function plug-in to be loaded at least includes a target version number and a target plug-in name, wherein the target version number is a version number of the function plug-in to be loaded, and the target plug-in name is a plug-in name of the function plug-in to be loaded; a determining unit, configured to determine at least one target application plug-in information from a plurality of application plug-in information in a user plug-in version library according to the target plug-in name, and determine a target plug-in slot, wherein the target application plug-in information is the application plug-in information corresponding to the plug-in name that is the same as the target plug-in name, and the application plug-in information includes the plug-in name and version number corresponding to the application plug-in, the application is developed based on an application base, the application base includes a plurality of plug-in slots and an open interface, the target plug-in slot is one of the plurality of plug-in slots, the plug-in slot is used to load a function plug-in to implement a function of the function plug-in, and the open interface is used to provide a standard way to access the plug-in slot; A calling unit, configured to call the open interface and send the function plug-in information to be loaded to the target plug-in slot through the open interface if the target version number is higher than the version number of each target application plug-in information; The loading unit is used to load and run the to-be-loaded function plug-in information through the target plug-in slot to update the function plug-in in the target plug-in slot.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of claims 1 to 6.

Images