CN112860453B - Message management method, system, electronic device and storage medium - Google Patents
Message management method, system, electronic device and storage medium Download PDFInfo
- Publication number
- CN112860453B CN112860453B CN202110147888.1A CN202110147888A CN112860453B CN 112860453 B CN112860453 B CN 112860453B CN 202110147888 A CN202110147888 A CN 202110147888A CN 112860453 B CN112860453 B CN 112860453B
- Authority
- CN
- China
- Prior art keywords
- message
- component
- module
- interface
- message component
- 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
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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Abstract
The invention discloses a message management method, a message management system, electronic equipment and a storage medium. The method is applied to the process of client development, the first interface statement is carried out based on a single service scene, the message type of the service scene is obtained, the single message type is packaged to obtain the corresponding message component, the first interface is realized in the message component, the message component is loaded into the service scene for use, the situation of multiple messages and multiple scenes is split into one component for each message type of each scene, the development is simplified, the reusability and readability of the components can be enhanced, the coupling degree between the service scene and the message component is reduced, and the method is easy to maintain.
Description
Technical Field
The present invention relates to the field of terminal development, and in particular, to a method, a system, an electronic device, and a storage medium for managing messages.
Background
With the continuous iterative development of the platform in the converged communication, the message types integrated by the platform, the functions and interactions related to each message type are more and more abundant, and the scenes used by the message types are gradually increased, such as editing scenes of each message type during converged transmission, editing scenes of each converged message template, detail viewing scenes of each converged message template, simulated preview scenes of the content of each message type on a mobile terminal, content display scenes of each message type on a time axis, and the like.
Therefore, the burden of the business component for carrying and being responsible for completing the display, interaction and related logical operations of the message types in the business scene is more and more heavy, which is embodied by the sharp increase of the code amount, the increase and the complication of the code logic,
in actual development, a multi-message management component is usually extracted from a main service component and packaged to be responsible for display, interaction and related logic operation of all message types in the scene, but because all message type codes are mixed in the same component, the code readability is reduced, the maintenance and expansion difficulty is high, when a new message type needs to be expanded, the implementation of the multi-message packaging component needs to be read first, and a lot of places need to be considered, so that the expansion difficulty of the new message type is high.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art. Therefore, the invention provides a message management method, a message management system, an electronic device and a storage medium, which can improve the readability of codes, reduce the coupling degree between modules and components and are easy to maintain and expand.
The message management method according to the embodiment of the first aspect of the invention comprises the following steps: performing first interface declaration based on a single service scene, and acquiring the message type of the service scene; packaging the single message type to obtain a corresponding message component; implementing the first interface within the message component; and loading the message component into the service scene for use according to the realized first interface.
The message management method provided by the embodiment of the invention at least has the following beneficial effects: in the process of client development, a first interface statement is carried out based on a single service scene, the message type of the service scene is obtained, the single message type is packaged to obtain a corresponding message component, a first interface is realized in the message component, the message component is loaded into the service scene for use, the situation of multiple messages and multiple scenes is split into one component for each message type of each scene, the development is simplified, the reusability and readability of the components can be enhanced, the coupling degree between the service scene and the components is reduced, and the maintenance is easy.
According to some embodiments of the invention, further comprising: and processing the message assembly to obtain a configuration file.
According to some embodiments of the invention, comprising: analyzing the first export function in the configuration file to obtain the message component; and performing second interface declaration on the message component so that the second interface is realized in any module.
According to some embodiments of the invention, comprising: performing plug-in processing on the message assembly to obtain an example of the message assembly; and loading and using the corresponding message component instance according to the service scene.
According to some embodiments of the present invention, the performing plug-in processing on the message component to obtain an example of the message component includes: acquiring a configuration file obtained according to the processing of the message component, and analyzing a second export function in the configuration file to obtain an injectable object; configuring a preset injector according to an injectable object to obtain the instance of the message component.
According to some embodiments of the invention, the instance of the message component is encapsulated to generate a dynamic component; and loading the dynamic component for use.
A message management system according to an embodiment of the second aspect of the present invention includes: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for carrying out first interface declaration based on a single service scene and acquiring the message type of the service scene; the processing module is used for encapsulating the single message type to obtain a corresponding message component; an implementation module to implement the first interface within the message component; and the loading module is used for loading the message component into the service scene for use.
The message management system according to the embodiment of the invention at least has the following beneficial effects: the method comprises the steps of performing first interface declaration based on a single service scene in an acquisition module, acquiring the message type of the service scene, packaging the single message type in a message module to obtain a corresponding message component, realizing the first interface in the message component, and finally loading the message component in a loading module to the service scene for use.
According to some embodiments of the invention, further comprising: and the configuration module is used for processing the message component to obtain a configuration file.
According to the electronic equipment of the third aspect embodiment of the invention, at least one processor, and, the memorizer connected with said at least one processor communication; wherein the memory stores instructions for execution by the at least one processor to cause the at least one processor to implement the message management method as described in the first aspect when executing the instructions.
According to the electronic equipment provided by the embodiment of the invention, at least the following beneficial effects are achieved: by executing the message management method according to the embodiment of the first aspect, reusability and readability of the components can be enhanced, coupling degree between a service scene and the components is reduced, and maintenance is facilitated.
According to a fourth aspect of the present invention, there is provided a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the message management method according to the first aspect.
The computer-readable storage medium according to the embodiment of the invention has at least the following advantages: by executing the message management method according to the embodiment of the first aspect, reusability and readability of the components can be enhanced, coupling degree between a service scene and the components is reduced, and maintenance is facilitated.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The invention is further described with reference to the following figures and examples, in which:
fig. 1 is a flowchart illustrating a message management method according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating a message management method according to a second embodiment of the present invention;
fig. 3 is a flowchart illustrating a message management method according to a third embodiment of the present invention;
fig. 4 is a flowchart illustrating a fourth embodiment of a message management method according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a specific process of step S340 of the message management method according to the embodiment of the present invention;
fig. 6 is a flowchart illustrating a specific process of step S350 of the message management method according to the embodiment of the present invention;
FIG. 7 is a block diagram of a message management method according to an embodiment of the present invention;
fig. 8 is a schematic block diagram illustrating another embodiment of a message management method according to the present invention.
Reference numerals:
The device comprises an acquisition module 600, a processing module 700, an implementation module 800 and a loading module 900.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.
In the description of the present invention, it should be understood that the orientation or positional relationship referred to in the description of the orientation, such as the upper, lower, front, rear, left, right, etc., is based on the orientation or positional relationship shown in the drawings, and is only for convenience of description and simplification of description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention.
In the description of the present invention, the meaning of a plurality is one or more, the meaning of a plurality is two or more, and the above, below, exceeding, etc. are understood as excluding the present numbers, and the above, below, within, etc. are understood as including the present numbers. If the first and second are described for the purpose of distinguishing technical features, they are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated or implicitly indicating the precedence of the technical features indicated.
In the description of the present invention, reference to the description of the terms "one embodiment," "some embodiments," "an illustrative embodiment," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
In a first aspect, an embodiment of the present application provides a message management method, and referring to fig. 1, a flowchart illustrating a first specific embodiment of the message management method in the embodiment of the present invention is shown, where the message management method is applied to client development, and specifically includes the following steps:
step S100, performing first interface declaration based on a single service scene, and acquiring the message type of the service scene;
step S200, packaging the single message type to obtain a corresponding message component;
step S300, a first interface is realized in the message component;
and step S400, loading the message component into a service scene for use according to the realized first interface.
In step S100, a single service scenario refers to scenarios such as an optical axis during message editing, message sending detail display, or message interaction, a plurality of pages are available, a plurality of scenarios are available under a single page, the scenarios include different message types, and the message types may specifically be short messages, voice, mails, and the like. A first interface is declared for each business scene under a folder in a client development project, the interface is used for restricting common behaviors of all message types under the business scene, all message types under the same scene have uniform behaviors, for example, various assignments, view state setting, values and the like under an editing scene, and at this time, the behaviors and attributes of all message types under the scene can be restricted by defining the interface. Each first interface corresponds to a file.
In step S200, each message type in the scene is individually encapsulated to obtain a corresponding message component, and the internal attributes and the specific implementation details of the component are hidden and only externally disclosed through an interface.
In step S300, when creating a message component, a first interface file corresponding to the message component needs to be introduced into each message component, and the message component class is implemented as a first interface, and the implementation interface uses instance keywords to enforce the message component to implement the method of interface definition.
In some embodiments, in the subsequent development process, when a new message type is extended in a service scenario and the new message type is encapsulated to form a new message component, the new message component only needs to implement an interface of the service scenario and be configured in the service scenario, and does not need to be used on a main service component through a component tag or modify logic on the main service component regarding the message type, so that the development cost of developers can be reduced, the development time can be shortened, the coupling between components is reduced, and the maintenance is easy.
Specifically, 8 message types exist in a main scene of converged communication, content related to the message types is extracted and split into 8 message components in a main service component, and the 8 message components are respectively responsible for editing and realizing respective views, models and logics, so that the flexibility of component calling and using is enhanced.
In some embodiments, each message type in different service scenes cohesively realizes the display, interaction and logic functions of the message type component and the main service component, so that the coupling degree of the message type component and the main service component in each service scene is low, the main service component only needs to call an external public behavior method of the message component, the code amount is effectively reduced, the readability is high, the maintenance and expansion difficulty is reduced, and the reusability is high.
In step S400, a message component to be displayed in a service scene is loaded in a main service component, and one or more message components to be displayed may be loaded.
In some embodiments, taking a short message component interface in a scenario of editing a converged transmitted message as an example, when the converged message is transmitted, multiple messages may be transmitted in a parallel or serial strategy, instead of being transmitted by using only a single message type, there are many message types in each scenario, for example, in an editing scenario, a main service component may simultaneously include edit views of many messages, and the edit views may be uniformly transmitted to an addressee after all edits are completed or a message template is selected, so that multiple message components that need to be dynamically loaded may be screened out in the editing scenario and displayed on a page, and the same may be true in other scenarios.
In the embodiment of the application, in the process of client development, a first interface statement is performed based on a single service scene, the message type of the service scene is acquired, the single message type is packaged to obtain a corresponding message component, a first interface is realized in the message component, the message component is loaded into the service scene for use, the situation of multiple messages and multiple scenes is split into one component for each message type of each scene, the development is simplified, the reusability and readability of the components can be enhanced, the coupling between the components and the service scene is reduced, and the maintenance is easy.
Referring to fig. 2, which shows a flowchart of a second specific embodiment of the message management method in the embodiment of the present invention, between step S300 and step S400, the method further includes: step S310, processing the message assembly to obtain a configuration file.
In step S310, a configuration file named shared-message module.ts may be created in the client development project, where the configuration file is used to manage import and export of all message type components and export of injectable objects, and the configuration file is independent into a file to be managed better, and the client development project is compiled and packaged as a whole and then placed on the server.
In particular, business development can be performed based on the Angular framework. A token which can be used in the DI provider is created for each scene in the configuration file, that is, a token is injected into each scene, so that the scene corresponds to the token, and a message component owned by each scene is defined for each business scene, where a developer can modify the message component owned by each scene to add a new message component. An injectable object is generated from the token definition key according to the message component definition value, a token and a message component as an array, and a first derivation function and a second derivation function are defined for deriving the message component and the injectable object, respectively. When a new message component needs to be expanded in one scene, the new message component can be directly configured into the management module, and the instances do not need to be sequentially created in the service scene using the new message component, so that the development process can be quicker and more convenient.
Referring to fig. 3, which shows a flowchart of a third specific embodiment of the message management method in the embodiment of the present invention, between step S310 and step S400, the method further includes:
step S320, analyzing the first export function in the configuration file to obtain a message component,
step S330, a second interface declaration is performed on the message component, so that the second interface is implemented in any module.
In step S320 and step S330, a second interface declaration is performed on the message component in a module named shared module, that is, the second interface declaration is performed in a declaration function of the shared module, and the message component is written in an export function export of the shared module, so that the second interface is implemented in any module.
Referring to fig. 4, which shows a flowchart of a fourth specific embodiment of the message management method in the embodiment of the present invention, between step S330 and step S400, the method specifically includes the steps of:
step S340, performing plug-in processing on the message assembly to obtain an example of the message assembly;
and step S350, loading and using the corresponding message component instance according to the service scene.
In step S340, configuring the message component 400 into a plug-in framework, where an injector in the plug-in framework automatically creates an example of the message component, and referring to fig. 5, a specific flowchart of step S340 of the message management method in the embodiment of the present invention is shown, which specifically includes the steps of:
step S341, obtaining a configuration file obtained by processing according to the message component;
step S342, analyzing the second export function in the configuration file to obtain an injectable object;
step S343, configuring a preset injector according to the injectable object, and obtaining an instance of the message component.
In step S341, step S342 and step S343, referring to fig. 7, a specific module diagram of the message management method in the embodiment of the present invention is shown, in the development project of the client, a file named AppModule is used as a project root module 100, and in the project root module 100 of a single page, the injectable object 500 is imported into the project root module 100, the injectable object 500 is configured in preset providers in the project root module 100, i.e., dependency provider 200, configures preset injector 300 using dependency provider 200, provider associates dependency items of various message types with injection token, injector 300 maintains a mapping table of internal token and provider, injector 300 will automatically create instances of dependencies depending on provider's configuration, thereby creating an instance of the message component 400 and injecting the instance into components, instructions, pipes, and other services.
In step S350, according to the current service scenario, a message component 400 that needs to be used is loaded, and referring to fig. 6, a specific flowchart of step S350 of the message management method in the embodiment of the present invention is shown, which specifically includes the steps of:
step S351, packaging the instance of the message component 400 to generate a dynamic component;
and step S352, loading the dynamic component for use.
In step S351 and step S352, the injector 300 corresponding to the instance of the message component 400 is found by Angualr according to the current service scenario, and the dependency provider 200 can be found in the root module 100 injector 300 according to the ModuleInjector hierarchy by the parsing rule of Angualr, so that the instance of the message component 400 can be taken out.
It should be noted that the multilevel injector of Angualr has two hierarchies, i.e., a ModuleInjector hierarchy and an elementinjjector hierarchy, and the use or annotation is configured in the ModuleInjector hierarchy, and the elementinjjector hierarchy is used in the parsing process.
The parsing rule of Angular is that when parsing a token for a component, Angualr is parsed in two stages, and first, it looks up through an elementinjecter hierarchy, and if no provider is found, it looks up through a ModuleInjector hierarchy, and in conjunction with the item of the embodiment of the present application, it instantiates its injector (elementinjecter) in a service component, and finds that there is no provider in its injector through the lookup, at this time, it will pass a request to the elementinjecter of its parent component, and according to the tree structure property of a single-page item component, it looks up in turn until the elementinjecter of the root component.
If the dependency is not found, the element of the request is returned to and looked up in the ModuleInjector hierarchy, and since the tree is also expanded from the root module 100 to the child service modules in the Angular single page project, the dependency provider 200 can be found in the root module 100 finally, and the configured scenario message component 400 can be taken.
According to the dynamic loading technology, the examples of the message components 400 which need to be used are packaged into dynamic components and are loaded for use, in practical application, the dynamic loading technology and the examples of the current message components 400 are packaged into a dynamic component loadervice service, namely the service can be used in each service component for dynamic loading, so that the code is simpler, and the component calling is more flexible.
In an actual application scenario, based on a message editing scenario, a user can select a service type in a page, configure a plurality of message types in policy information under the service type, and display message editing components corresponding to the message types, the user can fill in information or select a template for each message type, then select an addressee, fill in related information and configuration, that is, click a sending button to send a batch, and after the editing is completed, select to preview the edited content, and display the edited content on a mobile terminal according to the edited content of the message.
In a second aspect, an embodiment of the present invention further provides a message management system, and referring to fig. 8, a schematic diagram of another specific module of the message management method in the embodiment of the present invention is shown, where the obtaining module 600, the processing module 700, the implementing module 800, and the loading module 900 are used to perform a first interface declaration based on a single service scenario and obtain a message type of the service scenario, the processing module 700 is used to perform encapsulation processing on the single message type to obtain a corresponding message component, the implementing module 800 is used to implement a first interface in the message component, and the loading module 900 is used to load the message component into the service scenario for use.
In some embodiments, the message management system further includes a configuration module, and the configuration module is configured to process the message component to obtain the configuration file.
The specific functions and descriptions of the functional modules are discussed in detail in the embodiment of the first aspect, and thus are not described again.
In the embodiment of the present application, a first interface statement is performed in the obtaining module 600 based on a single service scenario and a message type of the service scenario is obtained, the single message type is encapsulated in the message module 700 to obtain a corresponding message component 400, a first interface is implemented in the message component 400, and finally the message component 400 is loaded into the service scenario in the loading module 900 for use.
In a third aspect, an embodiment of the present invention further provides an electronic device, including: at least one processor, and a memory communicatively coupled to the at least one processor;
wherein the processor is adapted to perform the message management method of the first aspect by invoking a computer program stored in the memory.
The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs and non-transitory computer executable programs, such as the message management method in the embodiments of the first aspect of the present invention. The processor implements the message management method in the above-described first embodiment by executing a non-transitory software program and instructions stored in the memory.
The memory may 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 a message management method that performs the above-described embodiment of the first aspect. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the terminal 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.
Non-transitory software programs and instructions required to implement the message management method in the first aspect embodiment described above are stored in a memory and, when executed by one or more processors, perform the message management method in the first aspect embodiment described above.
In a fourth aspect, embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions for: performing the message management method of the first aspect embodiment;
in some embodiments, the computer-readable storage medium stores computer-executable instructions, which when executed by one or more control processors, for example, by one of the processors in the electronic device of the third aspect, may cause the one or more processors to perform the message management method of the first aspect.
The above described embodiments of the device are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. 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 will appreciate that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the present invention is not limited to the above embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present invention. Furthermore, the embodiments of the present invention and the features of the embodiments may be combined with each other without conflict.
The embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the present invention is not limited to the above embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present invention. Furthermore, the embodiments of the present invention and the features of the embodiments may be combined with each other without conflict.
Claims (7)
1. The message management method is applied to client development and is characterized by comprising the following steps:
performing first interface declaration based on a single service scene, and acquiring the message type of the service scene;
packaging the single message type to obtain a corresponding message component;
implementing the first interface within the message component;
loading the message component into the service scene for use according to the realized first interface;
processing the message assembly to obtain a configuration file;
analyzing the first export function in the configuration file to obtain the message component;
and performing second interface declaration on the message component, wherein the second interface declaration is performed in a declaration function of a shared module, and the message component is written into an export function exports of the shared module, so that the second interface is realized in any module.
2. The message management method according to claim 1, comprising:
performing plug-in processing on the message assembly to obtain an example of the message assembly;
and loading and using the corresponding message component instance according to the service scene.
3. The message management method according to claim 2, wherein the plug-in processing the message component to obtain the instance of the message component comprises:
acquiring a configuration file obtained according to the processing of the message component;
analyzing a second export function in the configuration file to obtain an injectable object;
configuring a preset injector according to an injectable object to obtain the instance of the message component.
4. The message management method according to claim 2, wherein the loading and using the instance of the corresponding message component according to the service scenario includes:
generating a dynamic component by encapsulating the instance of the message component;
and loading the dynamic component for use.
5. A message management system, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for carrying out first interface declaration based on a single service scene and acquiring the message type of the service scene;
the processing module is used for encapsulating the single message type to obtain a corresponding message component;
an implementation module to implement the first interface within the message component;
the loading module is used for loading the message component into the service scene for use;
the configuration module is used for processing the message assembly to obtain a configuration file;
the processing module is further configured to analyze the first export function in the configuration file to obtain the message component;
the implementation module is further configured to perform a second interface declaration on the message component, where the second interface declaration is performed in a declaration function of a shared module, and the message component is written in an export function of the shared module, so that the second interface is implemented in any module.
6. An electronic device, comprising:
at least one processor, and,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions for execution by the at least one processor to cause the at least one processor, when executing the instructions, to implement the message management method of any of claims 1 to 4.
7. A computer-readable storage medium storing computer-executable instructions for causing a computer to perform the message management method of any one of claims 1 to 4.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011465185 | 2020-12-14 | ||
| CN2020114651855 | 2020-12-14 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112860453A CN112860453A (en) | 2021-05-28 |
| CN112860453B true CN112860453B (en) | 2022-04-08 |
Family
ID=75986488
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110147888.1A Active CN112860453B (en) | 2020-12-14 | 2021-02-03 | Message management method, system, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112860453B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113595872B (en) * | 2021-06-30 | 2023-06-16 | 百果园技术(新加坡)有限公司 | Message component configuration method, device, system, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9929996D0 (en) * | 1999-12-17 | 2000-02-09 | Inventec Corp | Method of using multi-step processing in message processing |
| WO2008054133A1 (en) * | 2006-10-31 | 2008-05-08 | Sk Telecom Co., Ltd. | Terminal having mutual api calling function in platform library, and dsl module generation method and api calling method using the same |
| CN101957755A (en) * | 2010-09-21 | 2011-01-26 | 用友软件股份有限公司 | Method and device for uniformly managing message |
| CN104317591A (en) * | 2014-10-23 | 2015-01-28 | 西安未来国际信息股份有限公司 | OSGi (open service gateway initiative)-based web interface frame system and web business processing method thereof |
| CN104536737A (en) * | 2014-12-16 | 2015-04-22 | 深圳市金证科技股份有限公司 | Program development framework based on assemblies |
| CN107329738A (en) * | 2017-05-25 | 2017-11-07 | 广州华多网络科技有限公司 | Component update method and device |
| CN108897632A (en) * | 2018-07-18 | 2018-11-27 | 杭州鑫合汇互联网金融服务有限公司 | A kind of message system and message method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6817010B2 (en) * | 2000-12-27 | 2004-11-09 | International Business Machines Corporation | Monitoring messages during execution of a message flow |
| US8825990B2 (en) * | 2011-01-27 | 2014-09-02 | Wyse Technology L.L.C. | Configuring and customizing a specific-purpose client having a windows-based embedded image using extensible markup language (XML) configuration |
| US10545747B2 (en) * | 2017-09-18 | 2020-01-28 | Rockwell Automation Technologies, Inc. | Application module deployment |
| US10162624B1 (en) * | 2017-12-15 | 2018-12-25 | Intuit Inc. | Web shell for dynamically generated cross-platform applications |
-
2021
- 2021-02-03 CN CN202110147888.1A patent/CN112860453B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9929996D0 (en) * | 1999-12-17 | 2000-02-09 | Inventec Corp | Method of using multi-step processing in message processing |
| WO2008054133A1 (en) * | 2006-10-31 | 2008-05-08 | Sk Telecom Co., Ltd. | Terminal having mutual api calling function in platform library, and dsl module generation method and api calling method using the same |
| CN101957755A (en) * | 2010-09-21 | 2011-01-26 | 用友软件股份有限公司 | Method and device for uniformly managing message |
| CN104317591A (en) * | 2014-10-23 | 2015-01-28 | 西安未来国际信息股份有限公司 | OSGi (open service gateway initiative)-based web interface frame system and web business processing method thereof |
| CN104536737A (en) * | 2014-12-16 | 2015-04-22 | 深圳市金证科技股份有限公司 | Program development framework based on assemblies |
| CN107329738A (en) * | 2017-05-25 | 2017-11-07 | 广州华多网络科技有限公司 | Component update method and device |
| CN108897632A (en) * | 2018-07-18 | 2018-11-27 | 杭州鑫合汇互联网金融服务有限公司 | A kind of message system and message method |
Non-Patent Citations (1)
| Title |
|---|
| 综合电子信息系统面向构件的软件开发与集成技术研究;柳永齐 等;《电子质量》;20181130(第11期);第42-44页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112860453A (en) | 2021-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| US9158510B2 (en) | System and computer program product for creating a telecommunications application | |
| US20090132220A1 (en) | Method For Creating A Telecommunications Application | |
| CN103150154B (en) | The implementation method and device of a kind of application plug | |
| CN108255545B (en) | Function calling method and device between components and modular architecture system | |
| CN110580174B (en) | Application component generation method, server and terminal | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| CN106648682A (en) | Dynamic-data general framework facing embedded system development | |
| CN112860453B (en) | Message management method, system, electronic device and storage medium | |
| CN113094028A (en) | Windows desktop program development framework, method and related components | |
| CN115993966A (en) | Application development system and method | |
| CN107133160B (en) | Server and client | |
| US11120513B2 (en) | Capital chain information traceability method, system, server and readable storage medium | |
| CN115269040B (en) | Tenant business application expanding method, device and system | |
| US8743116B1 (en) | Shader network | |
| CN116208676A (en) | Data back-source method, device, computer equipment, storage medium and program product | |
| CN114489674A (en) | Data verification method and device of dynamic data model | |
| CN114785847B (en) | Network control software development configuration method, terminal and storage medium | |
| TWI620134B (en) | Integration device and integration method thereof | |
| CN111459907A (en) | Method, system and storage medium for configuring master data through model | |
| CN116257227A (en) | Configurable topology implementation method and system based on resource capability center | |
| WO1999027447A1 (en) | Knowledge module | |
| CN114756309B (en) | Service calling method, framework, device and storage medium | |
| CN115269495B (en) | Business scheme metadata processing method and system based on aPaaS platform | |
| US20230289237A1 (en) | Automated nesting of existing stacks in a root stack within an aws environment |
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: 510308 room 23bd, No. 109, TIYU West Road, Tianhe District, Guangzhou City, Guangdong Province Applicant after: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. Address before: 510620 unit 01, 32F, building B, Victoria Plaza, 103 TIYU West Road, Tianhe District, Guangzhou City, Guangdong Province Applicant before: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |