CN108829380B - Method and device for realizing consistency of plug-in acquired information - Google Patents
Method and device for realizing consistency of plug-in acquired information Download PDFInfo
- Publication number
- CN108829380B CN108829380B CN201810550869.1A CN201810550869A CN108829380B CN 108829380 B CN108829380 B CN 108829380B CN 201810550869 A CN201810550869 A CN 201810550869A CN 108829380 B CN108829380 B CN 108829380B
- Authority
- CN
- China
- Prior art keywords
- target system
- docking
- class
- plug
- token
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000003032 molecular docking Methods 0.000 claims abstract description 93
- 238000004590 computer program Methods 0.000 claims description 6
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method for realizing consistency of plug-in acquired information, which comprises the following steps: creating a single-case mode docking plug-in; initializing the connector according to the received IP and Token of the target system so as to enable the docking connector to communicate with the target system; and when an input information acquisition command is received, acquiring the technical information of the target system through the docking plug-in and feeding the technical information back to the cloud platform. According to the technical scheme, when the information acquisition request of multiple users or multiple clients is faced, the information acquired by the multiple users or the multiple clients through a single class instance is consistent, so that the condition of inconsistent information is avoided; and the information obtained from the target system is not cached in the affinity class, so that the occupation of the system resources by the docking plug-in is reduced. The application also provides a device, equipment and a computer readable storage medium for realizing the consistency of the acquired information of the plug-in, and the beneficial effects are achieved.
Description
Technical Field
The present application relates to the field of plug-in management, and in particular, to a method, an apparatus, a device, and a computer-readable storage medium for implementing consistency of plug-in acquired information.
Background
The starting point of the plug-in technology is mainly to enable software to flexibly perform extended functions without recompiling and releasing a main program (framework program). The functionality of the software is determined by the framework and plug-ins. There is a specific interface between the framework and the plug-in, through which both must pass data or control information to implement the software functionality.
However, when the information acquisition request of multiple users or multiple clients is faced, the information of the target system acquired through the plug-in is inconsistent, and further, the situation that the acquired information is wrong is caused.
Disclosure of Invention
The application aims to provide a method, a device and equipment for realizing consistency of information acquired by plug-ins and a computer-readable storage medium, which are used for realizing consistency of information acquired by users or clients.
In order to solve the above technical problem, the present application provides a method for implementing consistency of plug-in acquired information, including:
creating a single-case mode docking plug-in;
initializing the docking plugin according to the received IP and Token of the target system so that the docking plugin can communicate with the target system;
and when an input information acquisition command is received, acquiring the technical information of the target system through the docking plug-in, and feeding the technical information back to the cloud platform.
Optionally, the creating a singleton-mode docking plugin includes:
establishing a docking class for docking with the cloud platform according to the requirement of the cloud platform;
a constructor of the affinity class with the unique instance is determined.
Optionally, initializing the docking plug-in according to the received IP and Token of the target system, including:
when the IP and the Token of the target system are received, judging whether the trust class with the unique instance exists in the docking plug-in;
if not, calling the constructor to create a trust class with a unique instance, and caching the IP and Token of the target system into the unique instance of the trust class;
and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the affinity class.
Optionally, when the affinity class with the unique instance exists, the method further includes:
deleting the affinity class with the unique instance;
calling the constructor to create a new affinity class with a unique instance, and caching the IP and Token of the target system into the unique instance of the new affinity class;
and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the new trust class.
Optionally, the initializing the docking plug-in according to the received IP and Token of the target system includes:
judging whether the IP and Token of the target system are correct or not;
if so, initializing the docking plug-in according to the IP and Token of the target system.
The present application further provides a device for achieving consistency of plug-in acquisition information, the device including:
the creating unit is used for creating the docking plug-in of the singleton mode;
the initialization unit is used for initializing the docking plugin according to the received IP and Token of the target system so as to enable the docking plugin to communicate with the target system;
and the acquisition and feedback unit is used for acquiring the technical information of the target system through the docking plug-in unit when receiving an input information acquisition command and feeding the technical information back to the cloud platform.
Optionally, the creating unit includes:
the first creating subunit is used for creating a docking class for docking with the cloud platform according to the requirement of the cloud platform;
and the determining subunit is used for determining the constructor of the affinity class with the unique instance.
Optionally, the initialization unit includes:
the first judgment subunit is used for judging whether the trust class with the unique instance exists in the docking plugin or not when the IP and Token of the target system are received;
the second creating subunit is used for calling the constructor to create the affinity class with the unique instance and caching the IP and Token of the target system into the unique instance of the affinity class when the affinity class with the unique instance does not exist in the docking plugin;
and the third creating subunit is used for creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the trust-in class.
The present application further provides an apparatus for implementing consistency of plug-in acquisition information, where the apparatus for implementing consistency of plug-in acquisition information includes:
a memory for storing a computer program;
a processor for implementing the steps of the method for consistent implementation of plug-in acquisition information when executing the computer program.
The present application further provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method for consistent implementation of plug-in acquired information as described in any of the above.
The method for realizing consistency of the plug-in acquired information comprises the following steps: creating a single-case mode docking plug-in; initializing the connector according to the received IP and Token of the target system so as to enable the docking connector to communicate with the target system; and when an input information acquisition command is received, acquiring the technical information of the target system through the docking plug-in and feeding the technical information back to the cloud platform.
According to the technical scheme provided by the application, a single-instance mode docking plugin is created, then the plugin is initialized according to the received IP and Token of the target system, so that the docking plugin can communicate with the target system, only one class instance is in the docking plugin, when an information acquisition request of multiple users or multiple clients is faced, the information acquired by the multiple users or the multiple clients through the class instance is consistent, and the condition of inconsistent information is avoided; in addition, any information obtained from the target system is not cached in the affinity class, and the technical information presented to the cloud platform by the target system is obtained in real time, so that the occupation of the system resources by the docking plug-in is reduced. The application also provides a device, equipment and computer readable storage medium for realizing consistency of the acquired information of the plug-in, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for implementing consistency of plug-in acquired information according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of an actual representation of S102 in the method for implementing consistency of plug-in acquired information provided in FIG. 1;
fig. 3 is a structural diagram of an apparatus for implementing consistency of plug-in acquisition information according to an embodiment of the present application;
fig. 4 is a structural diagram of another apparatus for implementing consistency of plug-in acquired information according to an embodiment of the present application;
fig. 5 is a structural diagram of a device for implementing consistency of plug-in acquired information according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a method, a device, equipment and a computer readable storage medium for realizing consistency of information acquired by plug-ins, which are used for realizing consistency of information acquired among users or platforms and reducing resource occupation of the plug-ins.
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.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for implementing consistency of plug-in information acquisition according to an embodiment of the present disclosure.
The method specifically comprises the following steps:
s101: creating a single-case mode docking plug-in;
the method for achieving consistency of the acquired information of the plug-ins is used for achieving consistency of the acquired information of all users or all platforms;
the single-case mode docking plug-in mentioned here is specifically a docking plug-in established by combining Java single-case mode with RESTAPI, and the single-case mode ensures that a certain class has only one instance and instantiates and provides the instance to the whole system by itself. For example, there may be several printers per computer, but only one Printer spooller, to avoid two print jobs being output to the Printer at the same time. There may be several communication ports per computer and the system should manage these communication ports centrally to avoid one communication port being called by two requests simultaneously.
Preferably, the docking plug-in for creating the singleton schema mentioned here may specifically be:
establishing a docking class for docking with the cloud platform according to the requirement of the cloud platform;
a constructor of the affinity class with the unique instance is determined.
Preferably, in order to ensure the minimum occupation of the system resources by the docking class, the method provided by the application can only implement a necessary method in the docking class without allocating any additional system resources, and all the plug-in technologies are implemented by a self-defined affinity class and a client class, that is, in the creation process of the docking class instance, only a default constructor of a parent class of the docking class is used, no additional system resources are allocated, and resources are not cached. The docking class is implemented by a unique instance of the trust-in class when presenting the plug-in technology details.
S102: initializing the connector according to the received IP and Token of the target system so as to enable the docking connector to communicate with the target system;
after the creation process of the docking plugin is completed, initializing the docking plugin according to the received IP and Token of the target system, so that the docking plugin can operate in the cloud platform and communicate with the target system;
optionally, the initializing operation of the connector according to the received IP and Token of the target system may specifically be:
judging whether the IP and Token of the target system are correct or not;
if yes, initializing the docking plug-in according to the IP and Token of the target system.
Further, when the IP and Token of the target system are incorrect, prompt information can be sent to the cloud platform, so that the user can maintain the system in time.
S103: and when an input information acquisition command is received, acquiring the technical information of the target system through the docking plug-in and feeding the technical information back to the cloud platform.
When an input information acquisition command is received, technical information of a target system is acquired through the docking plug-in, and the technical information is fed back to the cloud platform, so that the task of information acquisition is completed.
Optionally, the communication between the plug-in and the target system can be realized by using a HTTP-based CRUD method through an RESTAPI protocol, so that a CS architecture is formed between the docking plug-in and the target system, and the related function of the REST client is realized in the docking plug-in;
the technical information of the plug-in obtained from the target system is not cached in the affinity class with the unique instance, so that the technical information presented to the cloud platform by the target system is obtained in real time through the unique instance, namely only the IP and Token of the target system are cached in the docking plug-in, the rest information of the target system is not cached in the docking plug-in, but is directly presented to the cloud platform through the unique instance, and the occupation of system resources by the docking plug-in is reduced.
Based on the technical scheme, the method for achieving consistency of plug-in acquired information provided by the application comprises the steps of firstly creating a single-instance mode docking plug-in, and then initializing the plug-in according to the received IP and Token of a target system so as to enable the docking plug-in to be capable of communicating with the target system, so that only one class instance exists in the docking plug-in, when facing an information acquisition request of multiple users or multiple clients, the information acquired by the multiple users or the multiple clients through the class instance is consistent, and the condition of inconsistent information is avoided; in addition, any information obtained from the target system is not cached in the affinity class, and the technical information presented to the cloud platform by the target system is obtained in real time, so that the occupation of the system resources by the docking plug-in is reduced.
Based on the fact that the plug-in the prior art occupies too high system resources, and the system resources are very limited, the plug-in also has important significance in reducing the occupation of the system resources;
with respect to step S102 of the previous embodiment, there are various ways to perform initialization operation on the socket connector, and in order to reduce the occupation of system resources by the socket connector, a preferred way is taken as an example and is described in detail below with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flowchart illustrating an actual representation manner of S102 in the method for implementing consistency of plug-in acquisition information provided in fig. 1.
The method specifically comprises the following steps:
s201: when the IP and Token of the target system are received, judging whether a trust class with a unique example exists in the docking plug-in;
if not, go to step S202;
optionally, when the affinity class with the unique instance exists in the docking plug-in, the method further includes:
deleting the affinity class with the unique instance;
calling a constructor to create a new affinity class with a unique instance, and caching the IP and Token of the target system into the unique instance of the new affinity class;
and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the new trust class.
S202: calling a constructor to create a trust class with a unique instance, and caching the IP and Token of the target system into the unique instance of the trust class;
s203: and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the trust-in class.
Based on the technical scheme, when the IP and Token of the target system are received, whether the trust class with the unique instance exists in the docking plug-in is judged firstly; if yes, deleting and reestablishing a new intimacy class; and the IP and Token of the target system are cached into the unique instance, and the client class instance for communicating with the target system is created at the same time, so that whenever the docking plug-in has at most one trust class and one client class instance, the occupation of the plug-in on system resources is greatly reduced.
Referring to fig. 3, fig. 3 is a structural diagram of an apparatus for implementing consistency of plug-in acquisition information according to an embodiment of the present application.
The apparatus may include:
a creating unit 100, configured to create a docking plugin in a singleton mode;
an initialization unit 200, configured to perform initialization operation on the socket connector according to the received IP and Token of the target system, so that the socket connector can communicate with the target system;
the obtaining and feedback unit 300 is configured to obtain technical information of the target system through the docking plug-in when receiving the input information obtaining command, and feed the technical information back to the cloud platform.
Referring to fig. 4, fig. 4 is a structural diagram of another apparatus for implementing consistency of plug-in acquired information according to an embodiment of the present application.
The creating unit 100 may include:
the first establishing subunit is used for establishing a docking class for docking with the cloud platform according to the requirement of the cloud platform;
and the determining subunit is used for determining the constructor of the affinity class with the unique instance.
The initialization unit 200 may include:
the first judgment subunit is used for judging whether the trust class with the unique instance exists in the docking plugin or not when the IP and Token of the target system are received;
the second creating subunit is used for calling the constructor to create the affinity class with the unique instance and caching the IP and Token of the target system into the unique instance of the affinity class when the affinity class with the unique instance does not exist in the docking plugin;
and the third creating subunit is used for creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the trust class.
The initialization unit 200 may further include:
a deletion subunit configured to delete the affinity class having the unique instance;
the fourth creating subunit is used for calling the constructor to create a new affinity class with a unique instance, and caching the IP and Token of the target system into the unique instance of the new affinity class;
and the fifth creating subunit is used for creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the new trust class.
Further, the initialization unit 200 may also include:
the second judgment subunit is used for judging whether the IP and Token of the target system are correct or not;
and the initialization subunit is used for carrying out initialization operation on the docking plug-in according to the IP and Token of the target system when the IP and Token of the target system are correct.
The above components of the apparatus can be practically applied to the following embodiments:
the first creating subunit establishes a docking class for docking with the cloud platform according to the requirement of the cloud platform; the determining subunit determines a constructor of the affinity class with the unique instance;
when the IP and the Token of the target system are received, the second judging subunit judges whether the IP and the Token of the target system are correct or not, and when the IP and the Token of the target system are correct, the initializing subunit initializes the butting plug-in according to the IP and the Token of the target system;
the first judgment subunit judges whether the docking plugin has a trust class with a unique example; when the only instance of the affinity class does not exist in the docking plugin, the second creating subunit calls a constructor to create the only instance of the affinity class with the only instance, and the IP and Token of the target system are cached to the only instance of the affinity class; the third creating subunit creates a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the affinity class; when the intimacy class with the unique instance exists in the docking plug-in, the deleting subunit deletes the intimacy class with the unique instance; the fourth creating subunit calls the constructor to create a new intimacy class with a unique example, and caches the IP and Token of the target system into the unique example of the new intimacy class; the fifth creating subunit creates a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the new intimacy class;
when an input information acquisition command is received, the acquisition and feedback unit acquires technical information of the target system through the docking plug-in unit and feeds the technical information back to the cloud platform.
Referring to fig. 5, fig. 5 is a structural diagram of an apparatus for implementing consistency of plug-in acquisition information according to an embodiment of the present application.
The devices of the plug-in acquisition information consistency implementation may vary significantly from configuration to configuration or from performance to performance, and may include one or more processors (CPUs) 422 (e.g., one or more processors) and memory 432, one or more storage media 430 (e.g., one or more mass storage devices) storing applications 442 or data 444. Wherein the memory 432 and storage medium 430 may be transient or persistent storage. The program stored on the storage medium 430 may include one or more units (not shown), each of which may include a series of instruction operations for the apparatus. Still further, the central processor 422 may be arranged to communicate with the storage medium 430, and to execute a series of instruction operations in the storage medium 430 on the device 400 for plug-in retrieval of information consistency implementations.
The apparatus 400 of the plug-in get information consistency implementation may also include one or more power supplies 426, one or more wired or wireless network interfaces 450, one or more input-output interfaces 458, and/or one or more operating systems 441, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.
The steps in the method for implementing consistency of plug-in acquired information described in fig. 1 to 2 are implemented by the device for implementing consistency of plug-in acquired information based on the structure shown in fig. 5.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a function calling device, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The method, the apparatus, the device and the computer-readable storage medium for implementing consistency of plug-in acquired information provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are 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.
Claims (6)
1. A method for realizing consistency of plug-in acquired information is characterized by comprising the following steps:
creating a single-case mode docking plug-in;
initializing the docking plugin according to the received IP and Token of the target system so that the docking plugin can communicate with the target system;
when an input information acquisition command is received, acquiring technical information of the target system through the docking plug-in, and feeding the technical information back to the cloud platform;
wherein the creating of the docking plugin for the singleton schema comprises:
establishing a docking class for docking with the cloud platform according to the requirement of the cloud platform;
determining a constructor of a trust class having a unique instance;
initializing the docking plugin according to the received IP and Token of the target system, including:
when the IP and the Token of the target system are received, judging whether the trust class with the unique instance exists in the docking plug-in;
if not, calling the constructor to create a trust class with a unique instance, and caching the IP and Token of the target system into the unique instance of the trust class;
and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the affinity class.
2. The method of claim 1, wherein when the affinity class with unique instance exists, further comprising:
deleting the affinity class with the unique instance;
calling the constructor to create a new affinity class with a unique instance, and caching the IP and Token of the target system into the unique instance of the new affinity class;
and creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the new trust class.
3. The method of claim 1, wherein the initializing the docking plugin according to the received IP and Token of the target system comprises:
judging whether the IP and Token of the target system are correct or not;
if so, initializing the docking plug-in according to the IP and Token of the target system.
4. An apparatus for implementing consistency of plug-in acquisition information, comprising:
the creating unit is used for creating the docking plug-in of the singleton mode;
the initialization unit is used for initializing the docking plugin according to the received IP and Token of the target system so as to enable the docking plugin to communicate with the target system;
the acquisition and feedback unit is used for acquiring the technical information of the target system through the docking plug-in unit when receiving an input information acquisition command and feeding the technical information back to the cloud platform;
wherein the creating unit includes:
the first creating subunit is used for creating a docking class for docking with the cloud platform according to the requirement of the cloud platform;
a determining subunit for determining a constructor of the affinity class having the unique instance;
wherein the initialization unit includes:
the first judgment subunit is used for judging whether the trust class with the unique instance exists in the docking plugin or not when the IP and Token of the target system are received;
the second creating subunit is used for calling the constructor to create the affinity class with the unique instance and caching the IP and Token of the target system into the unique instance of the affinity class when the affinity class with the unique instance does not exist in the docking plugin;
and the third creating subunit is used for creating a client class instance for communicating with the target system according to the IP and Token of the target system in the unique instance of the trust-in class.
5. An apparatus for implementing consistency of plug-in acquisition information, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method for consistent implementation of plug-in acquired information according to any one of claims 1 to 3 when executing the computer program.
6. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the method for plug-in acquisition information consistency implementation according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810550869.1A CN108829380B (en) | 2018-05-31 | 2018-05-31 | Method and device for realizing consistency of plug-in acquired information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810550869.1A CN108829380B (en) | 2018-05-31 | 2018-05-31 | Method and device for realizing consistency of plug-in acquired information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108829380A CN108829380A (en) | 2018-11-16 |
| CN108829380B true CN108829380B (en) | 2021-08-31 |
Family
ID=64146652
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810550869.1A Active CN108829380B (en) | 2018-05-31 | 2018-05-31 | Method and device for realizing consistency of plug-in acquired information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108829380B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102520967A (en) * | 2011-12-28 | 2012-06-27 | 深圳市融创天下科技股份有限公司 | Method, system and mobile terminal for creating and using mobile platform plug-in component |
| CN104424002A (en) * | 2013-09-10 | 2015-03-18 | 中国科学院声学研究所 | Dynamic component loading method and system based on plug-in mechanism |
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN107861715A (en) * | 2017-10-31 | 2018-03-30 | 山东中创软件商用中间件股份有限公司 | A kind of business sets up system and method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2001284882A1 (en) * | 2000-08-14 | 2002-02-25 | Peter H. Gien | System and method for facilitating signing by buyers in electronic commerce |
| US8327341B2 (en) * | 2007-05-31 | 2012-12-04 | Red Hat, Inc. | Integrating aspect oriented programming into the application server |
-
2018
- 2018-05-31 CN CN201810550869.1A patent/CN108829380B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102520967A (en) * | 2011-12-28 | 2012-06-27 | 深圳市融创天下科技股份有限公司 | Method, system and mobile terminal for creating and using mobile platform plug-in component |
| CN104424002A (en) * | 2013-09-10 | 2015-03-18 | 中国科学院声学研究所 | Dynamic component loading method and system based on plug-in mechanism |
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN107861715A (en) * | 2017-10-31 | 2018-03-30 | 山东中创软件商用中间件股份有限公司 | A kind of business sets up system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108829380A (en) | 2018-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109104467B (en) | Development environment construction method and device, platform system and storage medium | |
| US11556366B2 (en) | Container login method, apparatus, and storage medium | |
| CN109768871B (en) | Method for configuring multiple virtual network cards, host machine and storage medium | |
| US20190384678A1 (en) | System and method for managing backup and restore of objects over cloud platforms | |
| JP5627187B2 (en) | Information processing apparatus, information processing method, and program | |
| US20110276661A1 (en) | Methods and systems for delivering applications from a desktop operating system | |
| CN107580011B (en) | Data sharing method and desktop cloud server | |
| JP6018316B2 (en) | Terminal authentication registration system, terminal authentication registration method and program | |
| JP2005018782A (en) | Software image creation in distributed build environment | |
| US20160253158A1 (en) | Backend custom code extensibility | |
| US20190281112A1 (en) | System and method for orchestrating cloud platform operations | |
| CN111061432B (en) | Service migration method, device, equipment and readable storage medium | |
| CN111881476B (en) | Object storage control method, device, computer equipment and storage medium | |
| US20120054743A1 (en) | Information Processing Apparatus and Client Management Method | |
| CN108632354B (en) | Physical machine admission management method and device and cloud desktop management platform | |
| US11064078B2 (en) | Information processing system, user terminal, and electronic apparatus | |
| CN113239377A (en) | Authority control method, device, equipment and storage medium | |
| CN111506547A (en) | Folder loading method, device, equipment and medium | |
| WO2017041650A1 (en) | Method and device for extending distributed consistency service | |
| CN108829380B (en) | Method and device for realizing consistency of plug-in acquired information | |
| WO2024045646A1 (en) | Method, apparatus and system for managing cluster access permission | |
| JP6205013B1 (en) | Application usage system | |
| US10542119B2 (en) | Multi-geographical processing of user requests | |
| CN114860350B (en) | Data processing method and device based on cloud diskless tree-like mirror image | |
| CN113672333B (en) | Virtual machine hot cloning method, device, system, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |