CN114237765B - Functional component processing method, device, electronic equipment and medium - Google Patents
Functional component processing method, device, electronic equipment and medium Download PDFInfo
- Publication number
- CN114237765B CN114237765B CN202111607234.9A CN202111607234A CN114237765B CN 114237765 B CN114237765 B CN 114237765B CN 202111607234 A CN202111607234 A CN 202111607234A CN 114237765 B CN114237765 B CN 114237765B
- Authority
- CN
- China
- Prior art keywords
- component
- functional component
- interface
- abstract
- functional
- 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/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
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 disclosure provides a functional component processing method, which can be applied to the technical field of finance. The processing method of the functional component comprises the following steps: defining a function component interface corresponding to each function component in the at least one function component based on the at least one function component to obtain at least one function component interface; determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface; respectively creating abstract component instances based on at least one abstract component interface to obtain at least one abstract component instance; and processing the at least one functional component based on the at least one abstract component instance. The present disclosure also provides a functional component processing apparatus, device, storage medium, and program product.
Description
Technical Field
The present disclosure relates to the field of computer technology, and may be applied to the field of financial technology, and more particularly, to a functional component processing method, apparatus, device, medium, and program product.
Background
In the WEB development process of the server, after the requirements are determined, the used technical scheme and functional components are determined according to the requirements, however, once the functional components are fixedly used, the functional components are difficult to manage, and unified management or processing of functional software cannot be realized.
Disclosure of Invention
In view of the foregoing, the present disclosure provides a functional component processing method, apparatus, device, medium, and program product that improve the processing efficiency of functional components.
According to a first aspect of the present disclosure, there is provided a functional component processing method, including: defining a function component interface corresponding to each function component in at least one function component based on the at least one function component to obtain at least one function component interface; determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface; creating abstract component instances based on the at least one abstract component interface respectively to obtain at least one abstract component instance; and processing the at least one functional component based on the at least one abstract component instance.
According to an embodiment of the disclosure, the defining, based on at least one functional component, a functional component interface corresponding to each of the at least one functional component, to obtain at least one functional component interface includes: determining, based on at least one functional component, a tool corresponding to each of the at least one functional component; and obtaining the at least one functional component interface based on the tool corresponding to each of the at least one functional component.
According to an embodiment of the disclosure, the processing the at least one functional component based on the at least one abstract component instance comprises: registering the at least one abstract component instance into a preset component container; the preset component container is used for defining the identifier corresponding to each abstract component instance in the at least one abstract component instance to obtain at least one identifier; processing the at least one functional component according to the at least one identification.
According to an embodiment of the present disclosure, the processing the at least one functional component according to the at least one identification includes: creating an abstract component instance of the target functional component in the case that the user needs to replace the functional component; determining an identifier corresponding to the functional component to be replaced; and processing the at least one functional component according to the identification corresponding to the functional component to be replaced and the abstract component instance of the target functional component.
According to an embodiment of the disclosure, the method for processing a functional component further includes, before the defining, based on the at least one functional component, a functional component interface corresponding to each of the at least one functional component, obtaining at least one functional component interface: analyzing at least one target function and determining a feature set of the at least one target function; at least one functional component is determined from the feature set.
According to an embodiment of the present disclosure, the at least one abstract component interfaces each comprise: one or more of running the interface, closing the interface, and obtaining the interface; the operation interface is used for executing initialization of the functional component; the closing interface is used for executing the closing of the functional component; the acquisition interface is used for executing the acquisition function component instance.
A second aspect of the present disclosure provides a functional component processing apparatus, comprising: the first determining module is used for defining a functional component interface corresponding to each functional component in the at least one functional component based on the at least one functional component to obtain at least one functional component interface; the second determining module is used for determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface; the creating module is used for respectively creating abstract component instances based on the at least one abstract component interface to obtain at least one abstract component instance; and a processing module for processing the at least one functional component based on the at least one abstract component instance.
A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the functional component processing method described above.
A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described functional component processing method.
A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described functional component processing method.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates application scenario diagrams of functional component processing methods, apparatuses, devices, media and program products according to embodiments of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a functional component processing method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a schematic of the execution of alternative functional components according to an embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart of a method of functional component processing according to another embodiment of the present disclosure;
FIG. 5 schematically illustrates a block diagram of a functional component processing apparatus according to an embodiment of the present disclosure; and
fig. 6 schematically illustrates a block diagram of an electronic device adapted to implement a functional component processing method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a method and a device for processing functional components, which are used for defining functional component interfaces corresponding to each functional component in at least one functional component based on at least one functional component to obtain at least one functional component interface; determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface; respectively creating abstract component instances based on at least one abstract component interface to obtain at least one abstract component instance; and processing the at least one functional component based on the at least one abstract component instance. By abstracting the function component interfaces, more convenient processing of the function components, such as unified management of the lifecycle (start, shut down), acquisition methods, and replacement of the function components, can be achieved.
Fig. 1 schematically illustrates an application scenario diagram of a functional component processing method, apparatus, device, medium and program product according to an embodiment of the present disclosure.
As shown in fig. 1, an application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the functional component processing method provided by the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the functional component processing apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 105. The functional component processing method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the functional component processing apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
The functional component processing method of the disclosed embodiment will be described in detail below with reference to fig. 2 based on the scenario described in fig. 1.
Fig. 2 schematically illustrates a flow chart of a functional component processing method according to an embodiment of the present disclosure.
As shown in fig. 2, this embodiment includes operations S210 to S240, and the functional component processing method may be performed by a server.
In operation S210, a function component interface corresponding to each of the at least one function component is defined based on the at least one function component, resulting in at least one function component interface.
In operation S210, a function component interface corresponding to each of the at least one function component is defined, e.g., function component interfaces 1 and 2 are defined for a cache function, a result of the definition is that component interface 1 is a set cache, and component interface 2 is a delete cache.
In operation S210, the role of the component interface is determined, and a certain function (i.e., a defined function) is implemented through the defined component interface.
In operation S220, abstract component interfaces corresponding to the at least one functional component interface, respectively, are determined, resulting in at least one abstract component interface.
The functional components may no longer be maintained for various reasons, which may lead to serious safety problems.
In order to uniformly manage the life cycle and the acquisition method of all the functional components, abstract component interfaces are defined, and the abstract of the functional component interfaces is realized, so that a user can process or manage the functional components more conveniently and simply.
In operation S230, abstract component instances are created based on the at least one abstract component interface, respectively, resulting in at least one abstract component instance.
For example, an abstract component instance is created for each functional component. The abstract component instance can store a concrete functional component instance and comprises methods of initialization (running), closing, acquisition and the like of the functional component, thereby realizing the abstract of the functional component. For example, the abstract component instance b of the functional component a is created, and the abstract component instance b firstly stores the instance of the functional component a, and meanwhile, the methods of initializing (running), closing, acquiring and the like of the functional component a are realized.
In operation S240, at least one functional component is processed based on the at least one abstract component instance.
By abstracting the function component interfaces, more convenient processing of the function components, such as unified management of the lifecycle (start, shut down), acquisition methods, and replacement of the function components, can be achieved.
In the current development practice of the server side (such as the development practice of the go language server side), the quality of the functional components is uneven, so that the management of the functional software is very inconvenient. For example, in the development process of the server-side WEB, after the requirements are determined, the technical scheme and the functional components used are determined according to the requirements, such as the following functional components: 1. determining a WEB frame; 2. determining an ORM framework; 3. determining a cache component; 4. determining a message queue component; 5. determining a log component, etc. Once the functional components to be used are fixed, the future time for handling or replacement will be very difficult.
The processing method of the functional component provided by the embodiment can be realized through the go language, so that the abstraction and pluggable (namely, the replacement of the functional component) of the go language server functional component can be realized.
According to the functional component processing method provided by the embodiment, at least one functional component interface is obtained by defining the functional component interface corresponding to each functional component in at least one functional component based on at least one functional component; determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface; respectively creating abstract component instances based on at least one abstract component interface to obtain at least one abstract component instance; and processing at least one functional component based on at least one abstract component instance to implement functional component interface abstraction, thereby implementing more convenient processing of functional components, such as unified management of lifecycles (start, shut down), acquisition methods, and replacement of functional components, by abstracting functional component interfaces.
The at least one abstract component interfaces each comprise: one or more of running the interface, closing the interface, and obtaining the interface; the operation interface is used for executing initialization of the functional component; the closing interface is used for executing the closing of the functional component; the acquisition interface is used to execute an acquisition function component instance.
In order to uniformly manage the life cycle and the acquisition method of all the functional components, abstract component interfaces are defined, for example, abstract component interfaces corresponding to at least one functional component interface are respectively defined according to at least one functional component interface, for example, a component operation method, a component closing method and a component instance are defined. The abstract component interface may include one or more of three methods: if 1, the operation is used for initializing the functional component, if 2, the smooth closing operation is closed for acting the functional component, if 3, the acquisition component is used for conveniently acquiring the functional component example.
The functional component processing method provided by the embodiment of the invention can realize more convenient processing of the functional components, such as unified management of the life cycle (starting and closing) and acquisition methods of all the functional components by providing one or more of an operation interface, a closing interface and an acquisition interface.
Defining a function component interface corresponding to each of the at least one function component based on the at least one function component, obtaining at least one function component interface, comprising: determining, based on the at least one functional component, a tool corresponding to each of the at least one functional component; and deriving at least one functional component interface based on the tool corresponding to each of the at least one functional component.
The tool corresponding to each of the at least one functional component refers to a technical tool for implementing the corresponding functional component, and implementing the cache function may be performed by a technical tool database, or a cache server, or the like, i.e. selecting a certain technology for implementing the corresponding functional component.
For example, a technical choice, i.e. a selection tool, is made for a function in the system. Where some functions may be implemented by multiple technologies, each technology may implement a functional component interface capable of implementing the corresponding function.
For example, a defined cache component interface is implemented using a redis database: obtaining a Redis cache functional component by the cache; log interface defined using standard output implementation: and (5) Loggr to obtain a StdoutLoggr functional component.
According to the functional component processing method, the tool corresponding to each functional component in the at least one functional component can obtain at least one functional component interface, so that the functional component interface has corresponding functions.
Based on the at least one abstract component instance, processing the at least one functional component comprises: registering at least one abstract component instance into a preset component container; the preset component container is used for defining the identifier corresponding to each abstract component instance in at least one abstract component instance to obtain at least one identifier; at least one functional component is processed according to the at least one identification.
To use abstract component instances, a component container may be provided for customizing an identity corresponding to each of at least one abstract component instance, registering all abstract component instances in the component container, e.g., retrieving abstract component instances for scheduling using the identity ID.
To guarantee resource dependency among components, the component container may use a list data structure of go to preserve the registration order of the components. After the registration of the abstract component instance is completed, the initialization of the component may be performed. All registered abstract component instances in the component container can be operated in sequence, and the abstract component instance realizes the abstract component interface, so that the operation method of the abstract component can be called for initialization work. When the process is closed, the closing method of the abstract component instance needs to be sequentially called in the reverse order of the component registration in the component container to carry out smooth closing work. If the self-defined identification is utilized, the corresponding abstract component instance is obtained from the component container, and the abstract component instance realizes the abstract component interface, so that the corresponding functional component can be obtained by calling the component obtaining method of the abstract component interface.
According to the functional component processing method, by processing at least one functional component according to at least one identifier, unified management of all the functional components can be achieved, and a user can conveniently manage all the functional components of the component container.
Processing at least one functional component according to at least one identification, comprising: creating an abstract component instance of the target functional component in the case that the user needs to replace the functional component; determining an identifier corresponding to the functional component to be replaced; at least one functional component is processed according to the identification corresponding to the functional component to be replaced and the abstract component instance of the target functional component.
For example, in the event of subsequent development or demand changes, the functional components currently in use and fail to meet the demand.
FIG. 3 schematically illustrates a schematic of the execution of alternative functional components according to an embodiment of the present disclosure;
for example, in the case of subsequent development or demand change, currently used functional components and inability to meet demand, replacement demand may be generated.
The user sends the replacement requirement to the server 320 through the client 310; the server 320 processes the received replacement request, such as sending the functional component b to be replaced to the functional component device 330. The functional component means creates an abstract component instance of the target functional component a according to the user's requirements. It should be noted that, the method for creating the abstract component instance may be the method described in the foregoing embodiments, so the specific process of creating the abstract component instance is not specifically described herein. After the abstract component instance of the target functional component a is created, at least one functional component, that is, the replacement of the functional component is implemented according to the identifier corresponding to the functional component b to be replaced and the abstract component instance of the target functional component a, and a notification of completing the replacement of the functional component is sent to the client 310, so that the user manages or processes according to the new functional components.
The functional component processing method provided by the embodiment of the invention can easily replace the original functional component, and when the functional component needs to be replaced, the replacement can be completed only by realizing the corresponding interface with the new functional component, thereby realizing the pluggable effect.
The method for processing the functional components further comprises the step of defining the functional component interfaces corresponding to each functional component in the at least one functional component based on the at least one functional component, and obtaining at least one functional component interface: analyzing the at least one target function to determine a feature set of the at least one target function; at least one functional component is determined from the feature set.
For example, the functional components may be three functional components, namely a WEB frame, a cache, and a log.
For example, the main functions in the system are analyzed, the feature set of each function is summarized, and at least one functional component is determined, so that the functional component interfaces corresponding to each function are conveniently defined respectively. The function component 1 is defined as a cache component interface, the function component 2 is defined as a log component interface, and the like.
Fig. 4 schematically illustrates a flow chart of a functional component processing method according to another embodiment of the present disclosure.
As shown in fig. 4, this embodiment includes operations S401 to S408, and the functional component processing method may be performed by a server.
In operation S401, at least one target function is analyzed to determine a feature set of the at least one target function.
In operation S402, at least one functional component is determined from a feature set.
In operation S403, a function component interface corresponding to each of the at least one function component is defined based on the at least one function component, resulting in at least one function component interface.
At least one functional component interface is obtained based on the tool corresponding to each of the at least one functional component in operation S404.
In operation S405, abstract component interfaces corresponding to the at least one functional component interface, respectively, are determined, resulting in at least one abstract component interface.
In operation S406, abstract component instances are created based on the at least one abstract component interface, respectively, resulting in at least one abstract component instance.
Registering at least one abstract component instance in a preset component container in operation S407; the preset component container is used for defining the identifier corresponding to each abstract component instance in at least one abstract component instance to obtain at least one identifier.
In operation S408, at least one functional component is processed according to at least one identification. Such as replacement of functional components, etc.
According to the functional component processing method, at least one functional component is determined according to the feature set, so that abstraction of the functional component is achieved, and management or processing of the functional component by a user is facilitated.
Based on the functional component processing method, the disclosure also provides a functional component processing device. The device will be described in detail below in connection with fig. 5.
Fig. 5 schematically shows a block diagram of a functional component processing apparatus according to an embodiment of the present disclosure.
As shown in fig. 5, the functional component processing apparatus 500 of this embodiment includes a first determination module 510, a second determination module 520, a creation module 530, and a processing module 540.
A first determining module 510, configured to define, based on the at least one functional component, a functional component interface corresponding to each of the at least one functional component, and obtain at least one functional component interface; a second determining module 520, configured to determine abstract component interfaces corresponding to the at least one functional component interface, to obtain at least one abstract component interface; a creating module 530, configured to create abstract component instances based on at least one abstract component interface, respectively, to obtain at least one abstract component instance; and a processing module 540 for processing the at least one functional component based on the at least one abstract component instance.
In some embodiments, the functional component processing apparatus further comprises: the second generation module is used for responding to the received login information from the second server and generating a temporary bill corresponding to the second server under the condition that the instance corresponding to the first server is determined to be in an unregistered state; and the second sending module is used for sending the temporary bill corresponding to the second server to the first server so that the first server can determine the user information corresponding to the second server according to the temporary bill corresponding to the second server.
In some embodiments, the first determining module comprises: a first determination sub-module for determining, based on the at least one functional component, a tool corresponding to each of the at least one functional component; and a second determination submodule for obtaining at least one functional component interface based on the tool corresponding to each of the at least one functional component.
In some embodiments, the processing module comprises: the booklet injection module is used for registering at least one abstract component instance into a preset component container; the preset component container is used for defining the identifier corresponding to each abstract component instance in at least one abstract component instance to obtain at least one identifier; and the processing sub-module is used for processing at least one functional component according to the at least one identifier.
In some embodiments, a processing sub-module for creating an abstract component instance of the target functional component in the event that the user needs to replace the functional component; determining an identifier corresponding to the functional component to be replaced; at least one functional component is processed according to the identification corresponding to the functional component to be replaced and the abstract component instance of the target functional component.
In some embodiments, the functional component processing apparatus further comprises: an analysis determination module for defining a function component interface corresponding to each of the at least one function component based on the at least one function component, prior to deriving the at least one function component interface: analyzing the at least one target function to determine a feature set of the at least one target function; at least one functional component is determined from the feature set.
In some embodiments, the at least one abstract component interface each comprises: one or more of running the interface, closing the interface, and obtaining the interface; the operation interface is used for executing initialization of the functional component; the closing interface is used for executing the closing of the functional component; the acquisition interface is used to execute an acquisition function component instance.
According to an embodiment of the present disclosure, any of the plurality of modules of the first determining module 510, the second determining module 520, the creating module 530, and the processing module 540 may be combined in one module to be implemented, or any of the plurality of modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the first determination module 510, the second determination module 520, the creation module 530, and the processing module 540 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first determination module 510, the second determination module 520, the creation module 530, and the processing module 540 may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
Fig. 6 schematically illustrates a block diagram of an electronic device adapted to implement a functional component processing method according to an embodiment of the present disclosure.
As shown in fig. 6, an electronic device 600 according to an embodiment of the present disclosure includes a processor 601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. The processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 601 may also include on-board memory for caching purposes. The processor 601 may comprise a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the disclosure.
In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM602, and the RAM 603 are connected to each other through a bus 604. The processor 601 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM602 and/or the RAM 603. Note that the program may be stored in one or more memories other than the ROM602 and the RAM 603. The processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, the electronic device 600 may also include an input/output (I/O) interface 605, the input/output (I/O) interface 605 also being connected to the bus 604. The electronic device 600 may also include one or more of the following components connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM602 and/or RAM 603 and/or one or more memories other than ROM602 and RAM 603 described above.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to implement the item recommendation method provided by embodiments of the present disclosure.
The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 601. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and/or installed from the removable medium 611. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 601. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.
The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.
Claims (7)
1. A functional component processing method, comprising:
defining a function component interface corresponding to each function component in at least one function component based on the at least one function component to obtain at least one function component interface;
determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface;
creating abstract component instances based on the at least one abstract component interface respectively to obtain at least one abstract component instance; and
processing the at least one functional component based on the at least one abstract component instance;
wherein said processing said at least one functional component based on said at least one abstract component instance comprises:
registering the at least one abstract component instance into a preset component container; the preset component container is used for defining the identifier corresponding to each abstract component instance in the at least one abstract component instance to obtain at least one identifier;
processing the at least one functional component according to the at least one identification;
the at least one abstract component interfaces each comprise: one or more of running the interface, closing the interface, and obtaining the interface; the operation interface is used for executing initialization of the functional component; the closing interface is used for executing the closing of the functional component; the acquisition interface is used for executing the acquisition function component instance.
2. The method of claim 1, wherein the defining, based on the at least one functional component, a functional component interface corresponding to each of the at least one functional component, results in at least one functional component interface, comprising:
determining, based on at least one functional component, a tool corresponding to each of the at least one functional component; and
and obtaining the at least one functional component interface based on the tool corresponding to each functional component in the at least one functional component.
3. The method of claim 1, wherein the processing the at least one functional component according to the at least one identification comprises:
creating an abstract component instance of the target functional component in the case that the user needs to replace the functional component;
determining an identifier corresponding to the functional component to be replaced;
and processing the at least one functional component according to the identification corresponding to the functional component to be replaced and the abstract component instance of the target functional component.
4. The method of claim 1, further comprising, prior to the defining, based on the at least one functional component, a functional component interface corresponding to each of the at least one functional component, deriving at least one functional component interface:
analyzing at least one target function and determining a feature set of the at least one target function;
at least one functional component is determined from the feature set.
5. A functional component handling apparatus comprising:
the first determining module is used for defining a functional component interface corresponding to each functional component in the at least one functional component based on the at least one functional component to obtain at least one functional component interface;
the second determining module is used for determining abstract component interfaces corresponding to the at least one functional component interface respectively to obtain at least one abstract component interface;
the creating module is used for respectively creating abstract component instances based on the at least one abstract component interface to obtain at least one abstract component instance; and
a processing module for processing the at least one functional component based on the at least one abstract component instance;
wherein said processing said at least one functional component based on said at least one abstract component instance comprises:
registering the at least one abstract component instance into a preset component container; the preset component container is used for defining the identifier corresponding to each abstract component instance in the at least one abstract component instance to obtain at least one identifier;
processing the at least one functional component according to the at least one identification;
the at least one abstract component interfaces each comprise: one or more of running the interface, closing the interface, and obtaining the interface; the operation interface is used for executing initialization of the functional component; the closing interface is used for executing the closing of the functional component; the acquisition interface is used for executing the acquisition function component instance.
6. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-4.
7. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111607234.9A CN114237765B (en) | 2021-12-24 | 2021-12-24 | Functional component processing method, device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111607234.9A CN114237765B (en) | 2021-12-24 | 2021-12-24 | Functional component processing method, device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114237765A CN114237765A (en) | 2022-03-25 |
| CN114237765B true CN114237765B (en) | 2023-06-02 |
Family
ID=80763059
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111607234.9A Active CN114237765B (en) | 2021-12-24 | 2021-12-24 | Functional component processing method, device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114237765B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116298825B (en) * | 2023-05-08 | 2023-10-20 | 杭州长川科技股份有限公司 | Chip test system and method, device, drive access device and method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572095A (en) * | 2014-12-29 | 2015-04-29 | 天津大学 | Self-adaptive method for building Ajax application for end user |
| CN105162666A (en) * | 2015-09-06 | 2015-12-16 | 福建星网锐捷通讯股份有限公司 | Method and system for realizing open interface |
| CN109471693A (en) * | 2018-10-26 | 2019-03-15 | 沈阳欧瑞科技有限公司 | Proprietary component is mapped to method, medium and the equipment of Cross-border congestion management system |
-
2021
- 2021-12-24 CN CN202111607234.9A patent/CN114237765B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572095A (en) * | 2014-12-29 | 2015-04-29 | 天津大学 | Self-adaptive method for building Ajax application for end user |
| CN105162666A (en) * | 2015-09-06 | 2015-12-16 | 福建星网锐捷通讯股份有限公司 | Method and system for realizing open interface |
| CN109471693A (en) * | 2018-10-26 | 2019-03-15 | 沈阳欧瑞科技有限公司 | Proprietary component is mapped to method, medium and the equipment of Cross-border congestion management system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114237765A (en) | 2022-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10872000B2 (en) | Late connection binding for bots | |
| US10534581B2 (en) | Application deployment on a host platform based on text tags descriptive of application requirements | |
| US8838799B2 (en) | Command management in a networked computing environment | |
| CN115587575A (en) | Data table creation method, target data query method, device and equipment | |
| CN115357761A (en) | Link tracking method and device, electronic equipment and storage medium | |
| CN114237765B (en) | Functional component processing method, device, electronic equipment and medium | |
| CN113076224B (en) | Data backup method, data backup system, electronic device and readable storage medium | |
| US10877805B2 (en) | Optimization of memory usage by integration flows | |
| CN114237651A (en) | Installation method and device of cloud native application, electronic equipment and medium | |
| CN112947919A (en) | Method and device for constructing service model and processing service request | |
| US11556332B2 (en) | Application updating in a computing environment using a function deployment component | |
| CN113448570A (en) | Data processing method and device, electronic equipment and storage medium | |
| US9934019B1 (en) | Application function conversion to a service | |
| US9053230B2 (en) | Framework and repository for analysis of software products | |
| CN115760013A (en) | Operation and maintenance model construction method and device, electronic equipment and storage medium | |
| CN114490130A (en) | Message subscription method and device, electronic equipment and storage medium | |
| CN113448578A (en) | Page data processing method, processing system, electronic device and readable storage medium | |
| CN113986258A (en) | Service publishing method, device, equipment and storage medium | |
| CN113434572A (en) | Data query method, query system, device, storage medium and program product | |
| CN113326079A (en) | Service version switching method, switching device, electronic equipment and storage medium | |
| CN115484149B (en) | Network switching method, network switching device, electronic equipment and storage medium | |
| CN114268558B (en) | Method, device, equipment and medium for generating monitoring graph | |
| CN114363172B (en) | Decoupling management method, device, equipment and medium for container group | |
| US20210349902A1 (en) | Database query processing | |
| CN115878901A (en) | Code warehouse keyword searching method, device, 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 |