CN112685474A - Application management method, device, equipment and storage medium - Google Patents

Application management method, device, equipment and storage medium Download PDF

Info

Publication number
CN112685474A
CN112685474A CN202011611597.5A CN202011611597A CN112685474A CN 112685474 A CN112685474 A CN 112685474A CN 202011611597 A CN202011611597 A CN 202011611597A CN 112685474 A CN112685474 A CN 112685474A
Authority
CN
China
Prior art keywords
target
component
application
information
version
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011611597.5A
Other languages
Chinese (zh)
Inventor
郭彦辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Udsafe Technology Co ltd
Original Assignee
Beijing Udsafe Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Udsafe Technology Co ltd filed Critical Beijing Udsafe Technology Co ltd
Priority to CN202011611597.5A priority Critical patent/CN112685474A/en
Publication of CN112685474A publication Critical patent/CN112685474A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Stored Programmes (AREA)

Abstract

The invention discloses an application management method, an application management device, application management equipment and a storage medium, wherein the application management method comprises the following steps: receiving a downloading request sent by a terminal, wherein the downloading request comprises target version information; inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name; and acquiring a target application component according to the target storage position, and sending the target application component to the terminal. The embodiment of the invention can acquire the target storage position by inquiring the version configuration information and the storage mark information through the target version information in the downloading request and then acquire the target application component according to the target storage position, thereby being capable of quickly finding the required file and solving the problem that the file required by the user cannot be quickly found in the prior art.

Description

Application management method, device, equipment and storage medium
Technical Field
The present application relates to data management technologies, and in particular, to an application management method, apparatus, device, and storage medium.
Background
The sharing server can be directly used for file sharing and printing sharing between the Linux and the windows system, the version warehouse is a subset of the sharing server, the application version warehouse can achieve classified management, uploading and downloading of applications, a docker mirror image is generated, and application release is achieved. In the prior art, files uploaded to a version warehouse cannot be found quickly when being pulled or downloaded subsequently.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an application management method, apparatus, device and storage medium, which can quickly find a required file in a version repository.
In a first aspect, an embodiment of the present invention provides an application management method, including:
receiving a downloading request sent by a terminal, wherein the downloading request comprises target version information;
inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name;
and acquiring a target application component according to the target storage position, and sending the target application component to the terminal.
Further, before receiving the download request sent by the terminal, the method further includes:
storing the target application component and generating the version configuration information and the storage flag information of the target application component.
Further, after generating the version configuration information of the target application component, the method further includes:
judging whether a version configuration file of the target application component exists or not;
if the version configuration file exists, writing the version configuration information into the version configuration file;
and if the version configuration file does not exist, creating the version configuration file, and writing the version configuration information into the version configuration file.
Further, the sending the target application component to the terminal, where the storage tag information includes the target storage location and the check tag information, includes:
verifying the target application component according to the verification mark information;
and when the verification is successful, sending the target application component to the terminal.
Further, the check mark information includes at least one of a component attribute, a component size, a namespace of the component, and a message digest algorithm value of the component.
Further, the method further comprises:
receiving a modification request sent by the terminal;
determining whether the target application component is in a modification permission open state;
and when the target application component is in the modification permission open state, executing the modification request, and when the target application component is not in the modification permission open state, rejecting the modification request.
Further, after obtaining the target application component according to the target storage location, the method further includes:
manufacturing an application mirror image according to the target application component;
testing the application mirror image;
and when the test is successful, sending the application image to a server in the cluster.
In a second aspect, an embodiment of the present invention further provides an application management apparatus, including:
the system comprises a receiving module, a downloading module and a processing module, wherein the receiving module is used for receiving a downloading request sent by a terminal, and the downloading request comprises target version information;
the query module is used for querying version configuration information to obtain a target component name corresponding to the target version information and querying storage mark information to obtain a target storage position corresponding to the target component name;
and the acquisition module is used for acquiring a target application component according to the target storage position and sending the target application component to the terminal.
In a third aspect, an embodiment of the present invention further provides an application management device, including: a memory and a processor; the memory stores a computer program, and the processor implements the application management method according to any one of the embodiments of the present invention when executing the computer program.
In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the application management method according to any one of the embodiments of the present invention.
The embodiment of the invention receives a downloading request sent by a terminal, wherein the downloading request comprises target version information; inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name; and acquiring a target application component according to the target storage position, and sending the target application component to the terminal. The embodiment of the invention can acquire the target storage position by inquiring the version configuration information and the storage mark information through the target version information in the downloading request and then acquire the target application component according to the target storage position, thereby being capable of quickly finding the required file and solving the problem that the file required by the user cannot be quickly found in the prior art.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a flowchart of an application management method according to an embodiment of the present invention;
fig. 2 is a flowchart of an application management method according to a second embodiment of the present invention;
fig. 3 is a flowchart of an application management method according to a third embodiment of the present invention;
fig. 4 is a flowchart of an application management method according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an application management apparatus according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of an application management device according to a sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Example one
Fig. 1 is a flowchart of an application management method according to an embodiment of the present invention, where the embodiment is applicable to a case of managing an application version repository, and the method may be executed by an application management apparatus according to an embodiment of the present invention, where the apparatus may be implemented in a software and/or hardware manner, and in a specific embodiment, the apparatus may be integrated in a server, and the server may be a server corresponding to the version repository. The following embodiments will be described by taking the device integrated in a server as an example, and as shown in fig. 1, the method specifically includes the following steps:
s110, receiving a downloading request sent by the terminal, wherein the downloading request comprises target version information.
The terminal may be a mobile phone, a computer, a tablet computer, or the like, and may send an application download request to the server to download a desired application, for example, when the terminal needs to install a certain application or needs to update an installed certain application, the terminal may send the download request to the server, and the server receives the download request sent by the terminal. The target version information may refer to a version number of an application to be downloaded by the terminal.
Specifically, the user can select an application and an application version on the terminal to send a download request by touch and click. In this embodiment, the example that the terminal is a mobile phone is taken as an example, a user may select application software to be downloaded through an application store in the mobile phone, and the downloaded application software is a current latest version in general. That is, the user selects application software to be downloaded through the mobile phone application store, a download request transmitting server containing target version information is generated, and the server receives a download request transmitted by the mobile phone. In this embodiment, the user may also enter the mobile phone application software, and select the update application version in the application software to generate the download request. For example, if the user selects to download an application software through an application store in the mobile phone, the current version of the application software is 2.3.4, and the download request includes the current version information 2.3.4. The follow-up developer completes the update of the application software, releases 2.4.0 version, and the user generates a download request containing 2.4.0 version information by selecting the update of the application software.
S120, inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name.
The version configuration information includes different version information and component names corresponding to different versions. The target component name refers to the component name corresponding to different application software to be downloaded by a user. The storage mark information comprises mark information such as the name and the size of the corresponding component when the application component is uploaded and stored in the server, and storage position information of the application component in the server. The target storage position refers to the storage position of the components corresponding to different application software to be downloaded by a user in the server.
It should be noted that, before the step of querying version configuration information is executed, the present embodiment further includes storing different versions of application components in the server, and generating version configuration information and storage flag information of the different versions of application components.
Specifically, the target version information of the application software to be downloaded by the user is obtained in step S110, the target version information is searched for in the version configuration information, and the component name corresponding to the target version information is obtained according to the correspondence between the different version information and the component names of the different versions in the version configuration information. And searching the name of the target component in the storage mark information, and acquiring a target storage position corresponding to the name of the target component according to the corresponding relation between the names of the components with different versions in the storage mark information and the storage positions of the components with different versions.
S130, acquiring the target application component according to the target storage position, and sending the target application component to the terminal.
Specifically, the target storage location of the target application component in the server is obtained through step S130, the target application component is quickly searched and downloaded in the server according to the target storage location, and the target application component is sent to the terminal.
The embodiment of the invention receives a downloading request sent by a terminal, wherein the downloading request comprises target version information; inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name; and acquiring a target application component according to the target storage position, and sending the target application component to the terminal. The embodiment of the invention can acquire the target storage position by inquiring the version configuration information and the storage mark information through the target version information in the downloading request and then acquire the target application component according to the target storage position, thereby being capable of quickly finding the required file and solving the problem that the file required by the user cannot be quickly found in the prior art.
Example two
Fig. 2 is a flowchart of an application management method according to a second embodiment of the present invention, where this embodiment is applicable to a case of managing an application version repository, and the present embodiment is optimized based on the above embodiments, and reference may be made to any of the above embodiments for technical details that are not described in detail in this embodiment. In this embodiment, before receiving the download request sent by the terminal, the method further includes: and storing the target application component, and generating version configuration information and storage mark information of the target application component. After generating the version configuration information of the target application component, the method further comprises the following steps: judging whether a version configuration file of the target application component exists or not; if the version configuration file exists, writing the version configuration information into the version configuration file; and if the version configuration file does not exist, creating the version configuration file, and writing the version configuration information into the version configuration file.
As shown in fig. 2, the application management method of this embodiment specifically includes the following steps:
s210, storing the target application component, and generating version configuration information and storage mark information of the target application component.
Specifically, before downloading the updated application, different versions of the application components need to be uploaded to the server. Firstly, a user can upload an application component through an application management interface of a terminal, the application component is marked on the application management interface while the application component is uploaded, for example, the attribute, the name space, the file size and the like of a file can be marked, and the terminal sends the application component uploaded by the user and the marked information to a server, so that an accurate application file can be quickly found in the server during downloading. The application management interface in this embodiment may be understood as a terminal application management interface before uploading an application component to a server. After the application component is uploaded to the terminal application management interface, the application component is marked again, and the Message Digest Algorithm value (Message-Digest Algorithm 5, MD5) is marked. In this embodiment, the storage location of the application component to be uploaded to the server and the version information to which the application component belongs may be recorded in a manner of web interface form submission, and the application component is stored in a specified storage location in the server. In this embodiment, only the way of recording the application component related information is illustrated, but not limited.
Further, after the application components are stored in the designated storage location in the server, the server automatically generates version configuration information according to the stored version information of the application components and the corresponding component names. And generating storage mark information according to the marked information during uploading the application components and the corresponding storage position information of the application components, and storing the storage mark information in a relational database.
It should be noted that the servers in this embodiment are preferably a subset of the shared servers, and may also be referred to as a directory or a folder in the shared servers. Each developer may access the server while using a different system.
S220, judging whether a version configuration file of the target application component exists or not.
The version configuration file refers to a file containing version configuration information.
It should be noted that the application component uploaded to the server in this embodiment may be an original version of the application software, or may be an updated version. That is, the application component uploaded to the server may be the application component uploaded for the first time or the application component replaced by the subsequent update. When the application component is an original version, the version configuration file of the application does not exist in the server. By determining whether the check exists for a version configuration file, the integrity of the application component can be guaranteed.
And S230, if the version configuration file exists, writing the version configuration information into the version configuration file.
Specifically, it is checked whether a version configuration file exists in the server. And if the version configuration file already exists in the server, writing the version configuration information generated through the steps into the version configuration file.
S240, if the version configuration file does not exist, creating the version configuration file, and writing the version configuration information into the version configuration file.
Specifically, if the version configuration file does not exist in the server, the version configuration file is created and generated, and the version configuration information generated through the above steps is written into the version configuration file.
It should be noted that the version configuration file in this embodiment is stored in the server by default and is stored in the same level directory as the application component. The version configuration file contains version configuration information of all different application component versions, and when the number of the application versions is large and the version configuration information in the version configuration file is excessive, a new version configuration file can be generated to write the version configuration information. In this embodiment, a writing threshold of the version configuration file may be set in advance, and when the version configuration information written by the version configuration file exceeds the writing threshold, a new version configuration file is created and generated. In this embodiment, the creation and generation of the version configuration file are only illustrated, but not limited.
And S250, receiving a downloading request sent by the terminal, wherein the downloading request comprises target version information.
S260, inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name.
And S270, acquiring the target application component according to the target storage position, and sending the target application component to the terminal.
In this embodiment, steps S230 to S240 do not limit the execution order of the steps, and one of the steps is executed according to the determination result of step S220.
According to the technical scheme of the embodiment of the invention, corresponding version configuration information and storage mark information are generated while the target application component is stored, and the generated version configuration information is ensured to be written into the version configuration file by judging whether the version configuration file of the target application component exists or not, so that the integrity of the application component stored in the server is ensured.
EXAMPLE III
Fig. 3 is a flowchart of an application management method according to a third embodiment of the present invention, where this embodiment is applicable to a case of managing an application version repository, and the present embodiment is optimized based on the foregoing embodiment, and reference may be made to any of the foregoing embodiments for technical details that are not described in detail in this embodiment. In this embodiment, sending the target application component to the terminal includes: verifying the target application component according to the verification mark information; and when the verification is successful, sending the target application component to the terminal. After the target application component is acquired according to the target storage position, the method further comprises the following steps: manufacturing an application mirror image according to the target application component; testing the application mirror image; and when the test is successful, sending the application image to the server in the cluster.
As shown in fig. 3, the application management method of this embodiment specifically includes the following steps:
s310, receiving a downloading request sent by the terminal, wherein the downloading request comprises target version information.
S320, inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name.
S330, acquiring the target application component according to the target storage position, and verifying the target application component according to the verification mark information.
Wherein the check mark information includes at least one of a component attribute, a component size, a namespace of the component, and an MD5 value of the component.
Specifically, after the target application component is acquired according to the target storage location, the target application component needs to be checked according to the check mark information to ensure the correctness and integrity of the application component. The verification of the target application component may be performed based on one or more of the verification flag information. In this embodiment, the MD5 value of the component is taken as an example of the check mark information. And calculating the MD5 value of the acquired target application component, comparing the calculated MD5 value with the MD5 value stored in the relational database during the uploading of the application component, and if the two MD5 values are the same, indicating that the acquisition of the target application component is successful. In this embodiment, only the verification method of the target application component is illustrated, but not limited.
And S340, when the verification is successful, manufacturing an application mirror image according to the target application component.
Specifically, in the present embodiment, the application image is produced according to the application component by using the prior art, and the prior art method is not described in detail in this embodiment.
And S350, testing the application mirror image.
Specifically, in this embodiment, the application image is automatically distributed to the image test environment, and the application image state is tested. The mirror test environment may be understood as a running environment of an application mirror. That is, the application image may be automatically distributed to an image testing environment where the application image is run to complete testing of the application image.
And S360, when the test is successful, sending the application mirror image to the server in the cluster.
Specifically, if the application image can successfully run in the image test environment, the application image test is successful. And when the test is successful, distributing the application image to the application node for container replacement. And restarting the corresponding cluster to realize application updating.
According to the technical scheme of the embodiment of the invention, the target application component is verified through the verification mark information, the accuracy and the integrity of the application component are further ensured to be documented, the corresponding application mirror image is manufactured according to the obtained target application component, the application mirror image is tested, and when the test is successful, the application mirror image is sent to the server in the cluster for container replacement, so that the mirror image is quickly constructed and the application is released.
Example four
Fig. 4 is a flowchart of an application management method according to a fourth embodiment of the present invention, where this embodiment is applicable to a case of managing an application version repository, and the present embodiment is optimized based on the foregoing embodiment, and reference may be made to any of the foregoing embodiments for technical details that are not described in detail in this embodiment. In this embodiment, the application management method further includes: receiving a modification request sent by a terminal; determining whether the target application component is in a modification permission open state; and when the target application component is in the open state of the modification permission, executing the modification request, and when the target application component is not in the open state of the modification permission, refusing the modification request.
As shown in fig. 4, the application management method of this embodiment specifically includes the following steps:
and S410, receiving a modification request sent by the terminal.
Wherein, the modification request refers to a request for re-uploading the application component or continuously uploading the application component, which is sent by the terminal.
Specifically, the server receives a request for re-uploading the application component or continuously uploading the application component, which is sent by the terminal.
And S420, determining whether the target application component is in the modification permission open state.
Wherein, the modification permission open state refers to the state that the current target application component is uploading. It is also understood that the corresponding version configuration information does not complete the state of writing the version configuration file.
Specifically, whether the target application component in the server is uploaded or not is detected, or whether the version configuration information is written into the version configuration file or not is detected.
S430, when the target application component is in the modification permission open state, executing the modification request, and when the target application component is not in the modification permission open state, refusing the modification request.
When the target application component is determined to be in the open state of the modification authority, the uploading quote component can be resubmitted in the application management interface through the web interface form in a web uploading button mode, and the modification of the version information of the application component and the application component is completed. When the target application component is determined not to be in the modification permission open state, the version of the application component can not be modified any more.
S440, receiving a downloading request sent by the terminal, wherein the downloading request comprises target version information.
S450, inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name.
And S460, acquiring the target application component according to the target storage position, and sending the target application component to the terminal.
The technical scheme of the embodiment of the invention completes the modification of the target application component by determining whether the target application component is in the modification permission open state, finishes uploading and storing the target application component, refuses the modification request when the target application component is not in the modification permission open state, can ensure the integrity of the uploaded application component, and realizes the rapid construction of the mirror image and the release application by rapidly obtaining the complete target application component.
EXAMPLE five
Fig. 5 is a schematic structural diagram of an application management apparatus according to a fifth embodiment of the present invention. As shown in fig. 5, the application management apparatus specifically includes: a receiving module 510, a querying module 520, and an obtaining module 530.
The receiving module 510 is configured to receive a download request sent by a terminal, where the download request includes target version information.
The query module 520 is configured to query the version configuration information to obtain a target component name corresponding to the target version information, and query the storage tag information to obtain a target storage location corresponding to the target component name.
An obtaining module 530, configured to obtain the target application component according to the target storage location, and send the target application component to the terminal.
In the application management device provided by the fifth embodiment of the present invention, a receiving module receives a download request sent by a terminal, where the download request includes target version information; inquiring version configuration information through an inquiring module to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name; and acquiring the target application component according to the target storage position through the acquisition module, and sending the target application component to the terminal. According to the embodiment of the invention, the target storage position is obtained by inquiring the version configuration information and the storage mark information through the target version information, the target application component is obtained according to the target storage position, and the target application component is sent to the terminal to complete the downloading and updating of the application, so that the problems that the file required by a user cannot be quickly found and the mirror image cannot be quickly built in the prior art are solved, the required file can be quickly found in the version library, the mirror image can be quickly built, the application can be quickly released, and the integrity of the application component is ensured.
Further, the application management device further comprises a storage module, which is used for storing the target application component and generating the version configuration information and the storage mark information of the target application component before receiving the download request sent by the terminal.
Further, the application management device further comprises a judging module, configured to judge whether a version configuration file of the target application component exists after generating the version configuration information of the target application component; if the version configuration file exists, writing the version configuration information into the version configuration file; and if the version configuration file does not exist, creating the version configuration file, and writing the version configuration information into the version configuration file.
On the basis of the foregoing embodiment, the storage tag information includes a target storage location and check tag information, and the obtaining module 530 includes:
the verification unit is used for verifying the target application component according to the verification mark information;
and the sending unit is used for sending the target application component to the terminal when the verification is successful.
Further, the checkmark information includes at least one of a component attribute, a component size, a namespace of the component, and a message digest algorithm value of the component.
Further, the application management device further comprises a modification module for receiving a modification request sent by the terminal; determining whether the target application component is in a modification permission open state; and when the target application component is in the open state of the modification permission, executing the modification request, and when the target application component is not in the open state of the modification permission, refusing the modification request.
Furthermore, the application management device also comprises a production sending module, which is used for producing the application mirror image according to the target application component after the target application component is obtained according to the target storage position; testing the application mirror image; and when the test is successful, sending the application image to the server in the cluster.
The application management device provided by the embodiment can execute the application management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects for executing the application management method.
EXAMPLE six
Fig. 6 is a schematic structural diagram of an application management device according to a sixth embodiment of the present invention. As shown in fig. 6, the apparatus includes a processor 610, a memory 620, an input device 630, and an output device 640; the number of processors 610 in the device may be one or more, and one processor 610 is taken as an example in fig. 6; the processor 610, the memory 620, the input device, and the output device 640 of the apparatus may be connected by a bus or other means, and fig. 6 illustrates an example of a connection by a bus.
The memory 620, as a computer-readable storage medium, may be used for storing software programs, computer-executable programs, and modules, such as program modules corresponding to the application management method in the embodiment of the present invention (for example, the receiving module 510, the querying module 520, and the obtaining module 530 in the application management apparatus). The processor 610 executes various functional applications of the device and data processing by executing software programs, instructions, and modules stored in the memory 620, that is, implements the application management method described above.
The memory 620 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 620 can further include memory located remotely from the processor 610, which can be connected to the device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 630 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function controls of the device. The output device 640 may include a display device such as a display screen.
EXAMPLE seven
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a method for application management, the method including:
receiving a downloading request sent by a terminal, wherein the downloading request comprises target version information;
inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name;
and acquiring the target application component according to the target storage position, and sending the target application component to the terminal.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the method operations described above, and may also perform related operations in the application management method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the application management apparatus, each included unit and module are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. An application management method, comprising:
receiving a downloading request sent by a terminal, wherein the downloading request comprises target version information;
inquiring version configuration information to obtain a target component name corresponding to the target version information, and inquiring storage mark information to obtain a target storage position corresponding to the target component name;
and acquiring a target application component according to the target storage position, and sending the target application component to the terminal.
2. The application management method according to claim 1, further comprising, before receiving the download request sent by the terminal:
storing the target application component and generating the version configuration information and the storage flag information of the target application component.
3. The application management method according to claim 2, further comprising, after generating the version configuration information of the target application component:
judging whether a version configuration file of the target application component exists or not;
if the version configuration file exists, writing the version configuration information into the version configuration file;
and if the version configuration file does not exist, creating the version configuration file, and writing the version configuration information into the version configuration file.
4. The application management method according to claim 1, wherein the storage tag information includes the target storage location and check tag information, and the sending the target application component to the terminal includes:
verifying the target application component according to the verification mark information;
and when the verification is successful, sending the target application component to the terminal.
5. The application management method according to claim 4, wherein the check mark information includes at least one of a component attribute, a component size, a namespace of a component, and a message digest algorithm value of a component.
6. The application management method of claim 1, wherein the method further comprises:
receiving a modification request sent by the terminal;
determining whether the target application component is in a modification permission open state;
and when the target application component is in the modification permission open state, executing the modification request, and when the target application component is not in the modification permission open state, rejecting the modification request.
7. The application management method according to claim 1, further comprising, after retrieving the target application component according to the target storage location:
manufacturing an application mirror image according to the target application component;
testing the application mirror image;
and when the test is successful, sending the application image to a server in the cluster.
8. An application management apparatus, comprising:
the system comprises a receiving module, a downloading module and a processing module, wherein the receiving module is used for receiving a downloading request sent by a terminal, and the downloading request comprises target version information;
the query module is used for querying version configuration information to obtain a target component name corresponding to the target version information and querying storage mark information to obtain a target storage position corresponding to the target component name;
and the acquisition module is used for acquiring a target application component according to the target storage position and sending the target application component to the terminal.
9. An application management device comprising: a memory and a processor; the memory stores a computer program, wherein the processor implements the application management method of any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the application management method of any one of claims 1 to 7.
CN202011611597.5A 2020-12-30 2020-12-30 Application management method, device, equipment and storage medium Pending CN112685474A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011611597.5A CN112685474A (en) 2020-12-30 2020-12-30 Application management method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011611597.5A CN112685474A (en) 2020-12-30 2020-12-30 Application management method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112685474A true CN112685474A (en) 2021-04-20

Family

ID=75455157

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011611597.5A Pending CN112685474A (en) 2020-12-30 2020-12-30 Application management method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112685474A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113010208A (en) * 2021-04-28 2021-06-22 数字广东网络建设有限公司 Version information generation method, version information generation device, version information generation equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109240727A (en) * 2018-11-20 2019-01-18 世纪龙信息网络有限责任公司 Application program update method, apparatus, computer equipment and storage medium
CN109413186A (en) * 2018-10-31 2019-03-01 Oppo广东移动通信有限公司 Application program update method, terminal, server and system
CN111447248A (en) * 2019-01-16 2020-07-24 网宿科技股份有限公司 File transmission method and device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109413186A (en) * 2018-10-31 2019-03-01 Oppo广东移动通信有限公司 Application program update method, terminal, server and system
CN109240727A (en) * 2018-11-20 2019-01-18 世纪龙信息网络有限责任公司 Application program update method, apparatus, computer equipment and storage medium
CN111447248A (en) * 2019-01-16 2020-07-24 网宿科技股份有限公司 File transmission method and device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113010208A (en) * 2021-04-28 2021-06-22 数字广东网络建设有限公司 Version information generation method, version information generation device, version information generation equipment and storage medium
CN113010208B (en) * 2021-04-28 2023-12-19 数字广东网络建设有限公司 Version information generation method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
CN108089893B (en) Method and device for determining redundant resources, terminal equipment and storage medium
CN107729227B (en) Application program test range determining method, system, server and storage medium
CN106874281B (en) Method and device for realizing database read-write separation
JP2005078612A (en) File sharing system, and file transfer method between file sharing systems
CN110427386B (en) Data processing method, device and computer storage medium
JP2011191862A (en) File management apparatus, file management system, and file management program
CN114297201A (en) Data processing method and device of multistage association database and electronic equipment
CN112685474A (en) Application management method, device, equipment and storage medium
US10606805B2 (en) Object-level image query and retrieval
CN111274004B (en) Process instance management method and device and computer storage medium
CN111008873A (en) User determination method and device, electronic equipment and storage medium
US20150347402A1 (en) System and method for enabling a client system to generate file system operations on a file system data set using a virtual namespace
CN115129789A (en) Bucket index storage method, device and medium of distributed object storage system
CN115203260A (en) Abnormal data determination method and device, electronic equipment and storage medium
US11500837B1 (en) Automating optimizations for items in a hierarchical data store
CN114281688A (en) Codeless or low-code automatic case management method and device
CN115964061A (en) Plug-in updating method and device, electronic equipment and computer readable storage medium
CN113609168A (en) Data export method, device, terminal and readable storage medium
US11977487B2 (en) Data control device, storage system, and data control method
US11537559B2 (en) Client generated aggregated indices
CN113626409B (en) Test data processing method, device, equipment and storage medium
CN112000321B (en) Method and device for realizing undo and/or redo of three-dimensional detection software
CN110968267B (en) Data management method, device, server and system
CN112214694B (en) Visible node query method and device, terminal equipment and readable storage medium
CN113127549B (en) Incremental data synchronization method, device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination