CN111124610A - Method and device for calling application program in application container and storage medium - Google Patents
Method and device for calling application program in application container and storage medium Download PDFInfo
- Publication number
- CN111124610A CN111124610A CN201911317033.8A CN201911317033A CN111124610A CN 111124610 A CN111124610 A CN 111124610A CN 201911317033 A CN201911317033 A CN 201911317033A CN 111124610 A CN111124610 A CN 111124610A
- Authority
- CN
- China
- Prior art keywords
- function
- calling
- application
- call
- preset
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000004806 packaging method and process Methods 0.000 claims abstract description 31
- 238000005538 encapsulation Methods 0.000 claims abstract description 22
- 230000006870 function Effects 0.000 claims description 278
- 238000004590 computer program Methods 0.000 claims description 6
- 238000007726 management method Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012856 packing Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a method, a device and a storage medium for calling an application program in an application container, wherein the method comprises the following steps: acquiring a function code segment corresponding to a preset function in an application program in an application container; generating a function calling packaging file corresponding to the preset function according to the function code segment, wherein the calling packaging file comprises a function identifier corresponding to the preset function and function attribute information; registering the function calling encapsulation file in an application container; judging whether a calling instruction corresponding to a preset function is received or not, wherein the calling instruction comprises a function identifier and a calling parameter; and when the call instruction is received, calling a function code segment corresponding to the preset function of the application program in a function call encapsulation file corresponding to the function identifier in the call instruction, acquiring a value corresponding to the call parameter and returning. The method can reduce direct calling among the application programs and can uniformly manage the calling conditions among the application programs.
Description
Technical Field
The present application relates to the field of program calling technologies, and in particular, to a method and an apparatus for calling an application program in a container, and a storage medium.
Background
Today container technology is widely focused and more enterprises have started laying out or have adopted container technology to build their own cloud infrastructure.
Compared with the container technology, the container technology starts to be a little later in many traditional industries and internet enterprises, but the enterprises are rapidly advanced in the last two years along with the unprecedented fire heat of the attention of the containers, and the construction of the related capacity of the containers is greatly promoted.
When designing a new microservice application architecture with containers or how to retrofit existing applications, it should be understood which factors and associated characteristics must be considered by the enterprise when implementing the container platform.
The applicant finds that in the existing container, the calls between the applications are all direct communication, namely, the ports access each other, and the call situations between the applications lack unified management and statistics. It is not clear which callable methods each application provides, and it relies on writing a separate interface invocation document for the application or communicating directly with the application developer.
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, the application provides an application program calling method, an application program calling device and a storage medium in an application container.
In view of the above, in a first aspect, the present application provides a method for calling an application program in an application container, including:
acquiring a function code segment corresponding to a preset function in an application program in an application container;
generating a function calling packaging file corresponding to the preset function according to the function code segment, wherein the calling packaging file comprises a function identifier corresponding to the preset function and function attribute information;
registering the function calling encapsulation file in an application container;
judging whether a calling instruction corresponding to the preset function is received or not, wherein the calling instruction comprises a function identifier and a calling parameter;
when the call instruction is received, calling a function code segment corresponding to the preset function of the application program in a function call encapsulation file corresponding to the function identifier in the call instruction, acquiring a value corresponding to the call parameter and returning the value
Optionally, the method further comprises:
and after the function code segment corresponding to the preset function of the application program is called, recording a call log corresponding to the call.
The call log at least comprises call information, and the call information comprises: the method comprises the following steps of calling party identification, called party identification, calling time, calling parameters and values corresponding to the calling parameters.
Optionally, the method further comprises:
detecting whether a function calling query request is received, wherein the function calling query request carries a function identifier;
and querying historical calling information corresponding to the function identifier from the calling log.
Optionally, acquiring a function list of all functions in the application program;
judging whether functions in the function list have functions which can be called;
when there is a function that can be called, the function that can be called is determined as a preset function.
Optionally, the method further comprises:
acquiring history called records of all functions of the application program;
and determining one or more functions in the history called records as the preset functions.
Optionally, the functional code segment is source code; generating a function calling encapsulation file corresponding to the preset function according to the function code segment, wherein the function calling encapsulation file comprises:
reading function attribute information in the source code;
compiling the source code;
and packaging the compiled file and the function attribute information to be used as the function calling packaging file.
Optionally, registering the function call encapsulation file in an application container, including:
storing the function calling packaging file into the application container;
controlling the application container to load the function calling encapsulation file;
analyzing and extracting function attribute information in the function calling encapsulation file;
and adding the function identifier in the function attribute information into a function list in the application container.
In a second aspect, the present application provides an apparatus for calling an application program in an application container, including:
the acquisition unit is used for acquiring a function code segment corresponding to a preset function in an application program in the application container;
the file generating unit is used for generating a function calling packaging file corresponding to the preset function according to the function code segment, and the calling packaging file comprises function attribute information corresponding to the preset function;
the registration unit is used for registering the function calling packaging file into an application container;
the calling judgment unit is used for judging whether a calling instruction corresponding to the preset function is received or not;
and the calling unit is used for calling the function code segment corresponding to the preset function of the application program according to the function calling packaging file when the calling instruction is received.
In a third aspect, the present application provides an electronic device, comprising: the application container comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program realizes the steps of calling the method by the application program in the application container according to any embodiment of the first aspect when being executed by the processor.
In a fourth aspect, the present application further provides a computer-readable storage medium, on which a resource allocation program is stored, where the resource allocation program, when executed by a processor, implements the steps of the method for calling the application program in the application container provided in any embodiment of the first aspect
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the calling method of the application program in the application container, the function code segments of the preset functions are registered in the application container, and meanwhile, through providing a uniform calling mode, calling of the preset functions in the application program is simplified and standardized, meanwhile, unified management of calling conditions among the application programs can be achieved, and development and operation and maintenance efficiency during mutual calling among the application programs in the container is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flowchart of an application calling method in an application container according to an embodiment of the present application;
fig. 2 is another schematic flowchart of an application program calling method in an application container according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another method for calling an application program in an application container according to an embodiment of the present application;
fig. 4 is a schematic flowchart of another method for calling an application program in an application container according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an application calling device in an application container according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a schematic flowchart of an application program calling method in an application container according to an embodiment of the present application.
As shown in fig. 1, the method for calling an application program in an application container according to the embodiment of the present application includes the following steps.
S101, acquiring a function code segment corresponding to a preset function in an application program in an application container;
s102, generating a function calling packaging file corresponding to the preset function according to the function code segment, wherein the calling packaging file comprises a function identifier corresponding to the preset function and function attribute information;
s103, registering the function calling packaging file into an application container;
s104, judging whether a calling instruction corresponding to the preset function is received or not, wherein the calling instruction comprises a function identifier and a calling parameter;
and when the call instruction is received, executing the step S105, otherwise, ending.
And S105, calling a function code segment corresponding to the preset function of the application program in the function calling encapsulation file corresponding to the function identifier in the calling instruction, acquiring a value corresponding to the calling parameter and returning.
According to the calling method of the application program in the application container, the function code segments of the preset functions are registered in the application container, and meanwhile, through providing a uniform calling mode, calling of the preset functions in the application program is simplified and standardized, meanwhile, unified management of calling conditions among the application programs can be achieved, and development and operation and maintenance efficiency during mutual calling among the application programs in the container is improved.
The embodiment shown in fig. 1 will be described in detail below with reference to specific embodiments.
In another embodiment of the present application, the method may further include the steps of:
s201, acquiring a function code segment corresponding to a preset function in an application program in an application container.
The functional code segment may be a code segment corresponding to an existing function read from an application program, or may be a certain functional code segment in a functional code segment set written and stored by a programmer according to a certain preset function.
The function code can be registered in the application container, so that the application container can communicate with the affiliated application program, obtain a return value and the like corresponding to the preset function in the application program, and facilitate other application programs to call the preset function of the application program through the application container.
In the embodiment of the present application, the application program may have a plurality of functions, and the existing application program facilitates external invocation in the form of an API interface, for example: the external application B calls the function inside the application a through the API interface inside the application a, which requires that the external application B must know in advance which API interfaces the application a has inside. This approach does not facilitate calls between a large number of applications in the application container.
In the embodiment of the present application, the purpose is to directly place the function code corresponding to the function that can be called in the application program in the application container, and when calling the corresponding function, the function code can be directly called in the application container, that is, the return value corresponding to the function code segment can be obtained, and the function inside the application program does not need to be called through the API interface of the application program.
And S202, generating a function calling packaging file corresponding to the preset function according to the function code segment.
The calling packaging file comprises function attribute information corresponding to the preset function, and the function attribute information comprises: the method comprises the following steps of function description, method description, parameter description, returned result description and calling example, wherein the function identification can be the name or letter code of the function, and can also be function ID and the like; the functional description refers to a description of the function; the method description refers to a calling method when the capability is called; the parameter description refers to corresponding parameters during calling, and the returned result description mainly refers to a returned value in a returned result; the calling example is a virtual calling demonstration, so that technicians can more clearly understand the function of the corresponding function code of the packaging file through the calling example.
In the embodiment of the present application, the package file may correspond to an installation package for installing the function code into the application container.
In general, the function code is source code, and in this embodiment, as shown in fig. 2, the step may include the following steps:
s2021, reading the function attribute information in the source code;
s2022, compiling the source code;
and S2023, packaging the compiled file and the function attribute information to be used as the function calling packaging file.
S203, registering the function calling packaging file into an application container.
In the embodiment of the present application, as shown in fig. 3, the step may include the following steps:
s2031, storing the function calling packaging file into the application container.
In the application container, for convenience of management, a call folder for storing data related to function call can be independently set for each application program, and then the call package file can be stored in the call folder corresponding to the application program.
And S2032, controlling the application container to load the function call package file.
And loading the function calling package file in the application program to enable the program corresponding to the calling package file to run in the application container.
S2033, analyzing and extracting the function attribute information in the function calling package file.
In the embodiment of the present application, the function attribute information includes: function identification, function description, method description, parameter description, returned result description, calling example and the like.
S2034, adding the function identifier in the function attribute information into the function list in the application container.
In order to facilitate different application programs to quickly know how many callable functions are registered in the application container, a function list is also maintained in the application container, the function list comprises all callable functions registered in the application container, and once a new function is registered in the application container, the function list is updated, and a function identifier corresponding to the new function is added into the function list.
In practical application, before calling, the function list can be inquired, and when the required function identifier is inquired, the corresponding function attribute information is searched according to the function identifier, so that whether the function is a target function is determined, and then function calling can be completed conveniently and quickly.
And S204, judging whether a call instruction corresponding to the preset function is received.
The calling instruction carries a function identifier corresponding to a preset function, when all the received calling instructions are received, the function identifier in the calling instruction is extracted, if the function identifier corresponding to the preset function is contained, the calling instruction corresponding to the preset function is determined to be received, and in addition, the calling instruction also carries a calling parameter. And when the call instruction is received, executing the step S205, otherwise, ending or repeating the step S204 and continuously monitoring.
S205, the function calling encapsulation file corresponding to the function identifier in the calling instruction calls the function code segment corresponding to the preset function of the application program, and the value corresponding to the calling parameter is obtained and returned.
In the embodiment of the application, calling is carried out, the function calling packaging file sends a calling request to a corresponding application program, and after a calling request result is obtained, a corresponding return value is sent to an application container to complete a calling process.
In other embodiments of the present application, in order to facilitate further management of calls between applications in the application container, on the basis of the embodiment shown in fig. 1, referring to fig. 4, the method may further include the following steps:
and S106, after the function code segment corresponding to the preset function of the application program is called, recording a call log corresponding to the call.
In this embodiment of the present application, the call log at least includes call information, where the call information includes: the method comprises the following steps of calling party identification, called party identification, calling time, calling parameters and values corresponding to the calling parameters.
Since the call logs are recorded in detail each time, when a large number of call situations among the application programs need to be analyzed, the method can quickly acquire all call information through the call logs, and unified management is facilitated.
After having the call log, it is convenient to query a certain call in the following, for this reason, the method may further include the following steps:
s107, detecting whether a function calling inquiry request is received or not, wherein the calling inquiry request carries a function identifier;
s108, historical calling information corresponding to the function identification is inquired from the calling log.
In other embodiments of the present application, when determining which functions can be invoked, the following manners may be adopted, wherein the first manner includes:
1011, a function list of all functions in the application is obtained.
A function list is maintained inside the application program, and the function list contains all functions of the application program, and in order to distinguish the functions in the function list, information on whether each function can be called is also included in the function class table.
1012, judging whether the function in the function list has a function which can be called.
By including information on whether each function can be called in the function list, it can be quickly determined which functions can be called.
When there is a function that can be called, 1013 is performed, otherwise, it ends.
1013, determining the function that can be called as the preset function
The second mode comprises the following steps:
1014, acquiring the history called record of all functions of the application program.
1015, determining one or more functions in the history called record as the preset function.
Inside the application program, in order to facilitate the analysis of the function calling situation, a history calling record of each function is also stored, and the history called record at least comprises: a function identification of the called function. And then the preset functions which can be called can be found by inquiring the history called records.
Fig. 5 is a schematic structural diagram of an application calling device in an application container according to an embodiment of the present application. As shown in fig. 5, the apparatus for calling an application program in an application container includes: an acquisition unit 11, a file generation unit 12, a registration unit 13, a call judgment unit 14, and a call unit 15, wherein,
the acquiring unit 11 is configured to acquire a function code segment corresponding to a preset function in an application program in an application container;
the file generating unit 12 is configured to generate a function calling encapsulation file corresponding to the preset function according to the function code segment, where the calling encapsulation file includes function attribute information corresponding to the preset function;
a registering unit 13, configured to register the function call encapsulation file in an application container;
a call judging unit 14, configured to judge whether a call instruction corresponding to the preset function is received;
and the calling unit 15 is configured to call, when the calling instruction is received, a function code segment corresponding to a preset function of the application program according to the function call encapsulation file.
In an embodiment of the present application, the function attribute information includes: function identification, function description, method description, parameter description, return result description and call example.
In one embodiment of the present application, the apparatus further comprises:
and the log recording unit is used for recording a call log corresponding to the call after calling the function code segment corresponding to the preset function of the application program.
The call log at least comprises call information, and the call information comprises: the method comprises the following steps of calling party identification, called party identification, calling time, calling parameters and values corresponding to the calling parameters.
In another embodiment of the present application, the apparatus further comprises:
the device comprises a detection unit, a processing unit and a processing unit, wherein the detection unit is used for detecting whether a function calling inquiry request is received or not, and the calling inquiry request carries a function identifier;
and the query unit is used for querying the historical calling information corresponding to the function identifier from the calling log.
In another embodiment of the present application, the apparatus further comprises:
a list acquisition unit configured to acquire a function list of all functions in the application;
a list judging unit, configured to judge whether a function in the function list has a function that can be called;
a first function determining unit, configured to determine, when there is a function that can be called, the function that can be called as a preset function.
In another embodiment of the present application, the apparatus further comprises:
the record acquisition unit is used for acquiring the history called records of all functions of the application program;
and the second function determining unit is used for determining one or more functions in the history called records as the preset functions.
Referring to the embodiment shown in fig. 5, if the functional code segment is source code; the file generation unit may include:
an information reading unit, configured to read function attribute information in the source code;
the compiling unit is used for compiling the source code;
and the packing unit is used for packing the compiled file and the function attribute information to be used as the function calling packaging file.
The aforementioned registration unit may include:
the storage unit is used for storing the function calling packaging file into the application container;
the loading unit is used for controlling the application container to load the function calling packaging file;
the analysis unit is used for analyzing and extracting the function attribute information in the function calling packaging file;
and the list updating unit is used for adding the function identifier in the function attribute information into the function list in the application container.
An embodiment of the present application further provides an electronic device, including: memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of an application calling method in an application container as described in any of figures 1-4.
An embodiment of the present application further provides a computer-readable storage medium, where a resource allocation program is stored on the computer-readable storage medium, and when the resource allocation program is executed by a processor, the method for calling an application program in an application container according to any one of fig. 1 to 4 is implemented.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in a plurality of software and/or hardware when implementing the invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for apparatus or system embodiments, since they are substantially similar to method embodiments, they are described in relative terms, as long as they are described in partial descriptions of method embodiments. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
It should be appreciated that the invention is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An application program calling method in an application container is characterized by comprising the following steps:
acquiring a function code segment corresponding to a preset function in an application program in an application container;
generating a function calling packaging file corresponding to the preset function according to the function code segment, wherein the calling packaging file comprises a function identifier corresponding to the preset function and function attribute information;
registering the function calling encapsulation file in an application container;
judging whether a calling instruction corresponding to the preset function is received or not, wherein the calling instruction comprises a function identifier and a calling parameter;
and when the call instruction is received, calling a function code segment corresponding to the preset function of the application program in a function call encapsulation file corresponding to the function identifier in the call instruction, acquiring a value corresponding to the call parameter and returning.
2. The method of claim 1, wherein the functional attribute information comprises: functional descriptions, method descriptions, parameter descriptions, return result descriptions, and call examples.
3. The method of claim 2, further comprising:
and after the function code segment corresponding to the preset function of the application program is called, recording a call log corresponding to the call.
The call log at least comprises call information, and the call information comprises: the method comprises the following steps of calling party identification, called party identification, calling time, calling parameters and values corresponding to the calling parameters.
4. The method of claim 3, further comprising:
detecting whether a function calling query request is received, wherein the function calling query request carries a function identifier;
and querying historical calling information corresponding to the function identifier from the calling log.
5. The method of claim 2, further comprising:
acquiring a function list of all functions in the application program;
judging whether functions in the function list have functions which can be called;
when there is a function that can be called, the function that can be called is determined as a preset function.
6. The method of claim 2, further comprising:
acquiring history called records of all functions of the application program;
and determining one or more functions in the history called records as the preset functions.
7. The method of claim 2, wherein the functional code segment is source code; generating a function calling encapsulation file corresponding to the preset function according to the function code segment, wherein the function calling encapsulation file comprises:
reading function attribute information in the source code;
compiling the source code;
and packaging the compiled file and the function attribute information to be used as the function calling packaging file.
8. The method of claim 2, wherein registering the function call encapsulation file in an application container comprises:
storing the function calling packaging file into the application container;
controlling the application container to load the function calling encapsulation file;
analyzing and extracting function attribute information in the function calling encapsulation file;
and adding the function identifier in the function attribute information into a function list in the application container.
9. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program when executed by the processor implements the steps of an application calling method in an application container according to any of claims 1 to 8.
10. A computer-readable storage medium, having stored thereon a resource allocation program which, when executed by a processor, implements the method steps of an application invocation in an application container according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911317033.8A CN111124610B (en) | 2019-12-19 | 2019-12-19 | Application program calling method, device and storage medium in application container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911317033.8A CN111124610B (en) | 2019-12-19 | 2019-12-19 | Application program calling method, device and storage medium in application container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111124610A true CN111124610A (en) | 2020-05-08 |
| CN111124610B CN111124610B (en) | 2024-01-23 |
Family
ID=70500907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911317033.8A Active CN111124610B (en) | 2019-12-19 | 2019-12-19 | Application program calling method, device and storage medium in application container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111124610B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817492A (en) * | 2021-01-12 | 2021-05-18 | 张宇翔 | Application program management method and system in mobile terminal |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101441566A (en) * | 2008-11-18 | 2009-05-27 | 腾讯科技（深圳）有限公司 | Embedded type platform and method for dynamically linking program on the same |
| CN101964742A (en) * | 2009-07-24 | 2011-02-02 | 华为技术有限公司 | Method, system and device for using network open ability |
| CN103309728A (en) * | 2012-03-12 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Asynchronous request processing method and equipment |
| US20170206073A1 (en) * | 2016-01-15 | 2017-07-20 | Google Inc. | Managing delivery of code and dependent data using application containers |
| US9983891B1 (en) * | 2017-03-21 | 2018-05-29 | Veritas Technologies Llc | Systems and methods for distributing configuration templates with application containers |
-
2019
- 2019-12-19 CN CN201911317033.8A patent/CN111124610B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101441566A (en) * | 2008-11-18 | 2009-05-27 | 腾讯科技（深圳）有限公司 | Embedded type platform and method for dynamically linking program on the same |
| CN101964742A (en) * | 2009-07-24 | 2011-02-02 | 华为技术有限公司 | Method, system and device for using network open ability |
| CN103309728A (en) * | 2012-03-12 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Asynchronous request processing method and equipment |
| US20170206073A1 (en) * | 2016-01-15 | 2017-07-20 | Google Inc. | Managing delivery of code and dependent data using application containers |
| US9983891B1 (en) * | 2017-03-21 | 2018-05-29 | Veritas Technologies Llc | Systems and methods for distributing configuration templates with application containers |
Non-Patent Citations (2)
| Title |
|---|
| 严丽云等: "容器技术及可行应用场景分析", 广东通信技术 * |
| 张琦: "基于Docker的CaaS管理平台架构研究与设计", 计算机应用与软件 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817492A (en) * | 2021-01-12 | 2021-05-18 | 张宇翔 | Application program management method and system in mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111124610B (en) | 2024-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110032599B (en) | Data structure reading and updating method and device, and electronic equipment | |
| CN104102502B (en) | A kind of processing method that realizing heat deployment, device and server | |
| CN110032568B (en) | Data structure reading and updating method and device, and electronic equipment | |
| US10057331B2 (en) | Automatic abstraction of flow of control in a distributed virtualization platform | |
| CN113157315A (en) | Method, device, equipment and medium for identifying difference information of different versions of software | |
| US20120159515A1 (en) | Sharing object representations | |
| CN110795454A (en) | Service request method, device, server and storage medium | |
| CN111240772A (en) | Data processing method and device based on block chain and storage medium | |
| US8484204B2 (en) | Dynamic metadata | |
| CN111124610B (en) | Application program calling method, device and storage medium in application container | |
| CN110598419A (en) | Block chain client vulnerability mining method, device, equipment and storage medium | |
| CN105447040B (en) | Binary file management and updating method, device and system | |
| CN111352631B (en) | Interface compatibility detection method and device | |
| CN110515893A (en) | Date storage method, device, equipment and computer readable storage medium | |
| CN115544050A (en) | Operation log recording method, device, equipment and storage medium | |
| CN111026613B (en) | Log processing method and device | |
| WO2021096346A1 (en) | A computer-implemented system for management of container logs and its method thereof | |
| CN110188247B (en) | Information generation method, device, computer equipment and computer readable storage medium | |
| CN112559444A (en) | SQL (structured query language) file migration method and device, storage medium and equipment | |
| CN116501414B (en) | Resource control method, device, medium and computing equipment based on cloud platform | |
| US7779430B2 (en) | Method, system, and article of manufacture for providing service components | |
| CN113176876B (en) | Data reading and writing method and device and electronic equipment | |
| CN114595246B (en) | Statement generation method, device, equipment and storage medium | |
| CN115586902A (en) | Method, device, storage medium and equipment for detecting Python package dependency relationship | |
| CN103765383A (en) | Application interface for object build information |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room h8208, Hongxiang 1989 science, technology and Culture Industrial Park, Tangjialing Road, Haidian District, Beijing 100094 Applicant after: BEIJING ACTIONSOFT SCIENCE AND TECHNOLOGY DEVELOPMENT Co.,Ltd. Address before: 100085 Room 501, No.7, Shangdi Information Road, Haidian District, Beijing Applicant before: BEIJING ACTIONSOFT SCIENCE AND TECHNOLOGY DEVELOPMENT Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |