CN111984236A - Component standardization management method and device, computer equipment and readable storage medium - Google Patents
Component standardization management method and device, computer equipment and readable storage medium Download PDFInfo
- Publication number
- CN111984236A CN111984236A CN202010852276.8A CN202010852276A CN111984236A CN 111984236 A CN111984236 A CN 111984236A CN 202010852276 A CN202010852276 A CN 202010852276A CN 111984236 A CN111984236 A CN 111984236A
- Authority
- CN
- China
- Prior art keywords
- component
- standard
- calling
- providing
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 65
- 238000000034 method Methods 0.000 claims abstract description 55
- 230000008569 process Effects 0.000 claims abstract description 33
- 238000004891 communication Methods 0.000 claims abstract description 23
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 5
- 238000011161 development Methods 0.000 abstract description 5
- 238000013473 artificial intelligence Methods 0.000 abstract description 2
- 230000007246 mechanism Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012827 research and development Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000001066 destructive effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to artificial intelligence, and provides a component standardized management method, a device, computer equipment and a readable storage medium, wherein the method comprises the following steps: receiving a to-be-processed component sent by a providing user side and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component; receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal. The invention also relates to a blockchain technique, where information can be stored in blockchain nodes. The invention obtains the standard component for the component to be processed provided by the user side and obtains the corresponding standard component or standard module according to the calling request of the access user side, thereby avoiding the occurrence of the situation of repeated development of the computer system of the access user side.
Description
Technical Field
The invention relates to the technical field of artificial intelligence research and development management, in particular to a component standardization management method and device, computer equipment and a readable storage medium.
Background
Due to the diversity of business requirements of each organization, each organization body usually creates a computer system for solving its own business requirements to realize automatic execution of business operations in order to solve its business requirements.
Generally, a general computer module is often called for executing business operations, but each mechanism generally writes respective computer systems completely, so that the general module of each computer system is repeatedly developed, and resources are wasted.
Disclosure of Invention
The invention aims to provide a component standardized management method, a component standardized management device, computer equipment and a readable storage medium, relates to the field of module management of computer research and development management, and aims to solve the problem that in the prior art, because each mechanism can write respective computer systems completely, universal modules of the computer systems are repeatedly developed, and resources are wasted.
In order to achieve the above object, the present invention provides a method for standardized management of components, comprising:
receiving a to-be-processed component sent by a providing user side and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component;
receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal.
In the above solution, before receiving the to-be-processed component sent by the providing client and executing the providing client process, the method includes:
creating a component library for storing a database of components;
the component library stores the components in a key-value mode, wherein the id of each component is a key, and the component is a value.
In the above solution, the providing end process includes:
executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning the refusal providing information and ending;
executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component;
and sending the standard component to a preset component library.
In the above solution, the providing the authority thread includes:
extracting a component code of a component to be processed, and judging whether the component code belongs to a preset provision authority list; if yes, judging that the component to be processed is authorized; if not, returning the refusal providing information and ending; wherein, the component code records the ID information of the providing user side;
detecting whether the authorized component to be processed can normally run or not; if yes, judging the component to be processed to be an acceptable component; if not, returning the providing refusal information and ending.
In the above scheme, the access terminal process includes:
executing an access authority thread to judge whether the calling request has calling authority; if so, extracting the calling thread; if not, returning calling rejection information;
executing a calling thread to obtain a standard component from a component library according to the calling request and/or assembling the standard component to form a standard module;
and executing a communication thread to enable the obtained standard component or the standard module to establish communication connection with the access client.
In the above scheme, the access permission thread includes:
extracting a calling code of the calling request, and judging whether the calling code belongs to a preset access authority list or not; if yes, judging that the calling request has a calling authority; if not, returning the refusal providing information and ending; and the calling code records the ID information of the access user terminal.
In the foregoing solution, the invoking thread includes:
extracting the component ID in the calling request, and acquiring a standard component corresponding to the component ID from a component library;
judging whether the number of the obtained standard components is one or not; if so, ending the calling thread; if not, extracting the incidence relation in the calling request, and assembling the standard component according to the incidence relation to obtain a standard module.
In order to achieve the above object, the present invention further provides a device for standardized management of components, including:
the system comprises a providing end management module, a providing end processing module and a standard component acquisition module, wherein the providing end management module is used for receiving a to-be-processed component sent by a providing user end and executing a providing end process so as to construct an interface in the to-be-processed component to obtain the standard component;
the access terminal management module is used for receiving a calling request sent by an access user terminal and executing an access terminal process so as to acquire a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establish communication connection between the standard component or the standard module and the access user terminal.
In order to achieve the above object, the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor of the computer device implements the steps of the standardized management method of the above components when executing the computer program.
To achieve the above object, the present invention also provides a computer-readable storage medium including a storage data area storing data created according to use of a blockchain node and a storage program area storing a computer program, wherein the computer program stored in the storage medium implements the steps of the component standardized management method when executed by a processor.
The component standardization management method, the device, the computer equipment and the readable storage medium provided by the invention can enable the access user terminal to obtain a general computer module by obtaining the standard component for the component to be processed provided by the user terminal and obtaining the corresponding standard component or standard module according to the calling request of the access user terminal, namely: the standard component or the standard module avoids the situation that the computer system accessed to the user side is repeatedly developed, and further avoids the waste of computer resources and development resources.
Drawings
FIG. 1 is a flowchart of a component standardization management method according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating an environment application of a component standardization management method according to a second embodiment of the present application;
FIG. 3 is a flowchart of a second embodiment of the method for standardized management of components of the present invention;
FIG. 4 is a flowchart of a providing process according to a second embodiment of the component standardization management method of the present invention;
FIG. 5 is a flowchart of a thread providing authority according to a second embodiment of the component standardization management method of the present invention;
fig. 6 is a flowchart of an access terminal process according to a second embodiment of the component standardization management method of the present invention;
FIG. 7 is a flowchart of an access right thread according to a second embodiment of the component standardization management method of the present invention;
FIG. 8 is a flowchart of a thread calling according to a second embodiment of the method for standardized management of components of the present invention;
FIG. 9 is a block diagram of a third embodiment of a device for component standardization management according to the present invention;
fig. 10 is a schematic diagram of a hardware structure of a computer device according to a fourth embodiment of the present invention.
Reference numerals:
1. component standardization management device 2, server 3, providing user terminal 4, access user terminal
5. Computer device 11, creation module 12, and providing-side management module
13. Access terminal management module 51, memory 52, processor
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a component standardized management method, a device, computer equipment and a readable storage medium, which are suitable for the field of module management related to computer research and development management and provide a component standardized management method based on a creation module, a providing end management module and an access end management module. The method comprises the steps of receiving a to-be-processed component sent by a providing user side and executing a providing end process to construct an interface in the to-be-processed component to obtain a standard component; receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal.
The first embodiment is as follows:
referring to fig. 1, a method for component standardization management in this embodiment includes:
s102: receiving a to-be-processed component sent by a providing user side and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component;
s103: receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal.
In order to enable the access client to smoothly call the standard component, the interface is constructed in the component to be processed so that the access client can call the standard component, and the calling complexity of the standard component is greatly reduced.
The standard component is called for ensuring an access user side with calling authority, or a standard module formed by assembling a plurality of standard components is called, so that the access user side can obtain reliable standard components or standard modules.
Therefore, the standard component is obtained for the component to be processed provided by the user side, and the corresponding standard component or standard module is obtained according to the call request of the access user side, so that the access user side can obtain the general computer module, that is: the standard component or the standard module avoids the situation that computer equipment accessed to a user side is repeatedly developed, and further avoids the waste of computer resources and development resources.
Example two:
the embodiment is a specific application scenario of the first embodiment, and the method provided by the present invention can be more clearly and specifically explained through the embodiment.
The method provided in this embodiment is specifically described below by taking, as an example, a server running a component standardized management method, acquiring a standard component for a built interface in a to-be-processed component sent by a providing client, and acquiring the standard component according to a call request sent by an accessing client. It should be noted that the present embodiment is only exemplary, and does not limit the protection scope of the embodiments of the present invention.
Fig. 2 schematically shows an environment application diagram of the component standardization management method according to the second embodiment of the present application.
In an exemplary embodiment, the server 2 in which the component standardized management method is located provides the user end 3 and the access user end 4 respectively through a network, the server 2 may provide services through one or more networks, and the network may include various network devices such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. The network 3 may include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and/or the like. The network may include wireless links, such as cellular links, satellite links, Wi-Fi links, and/or the like; the providing user end 3 and the accessing user end 4 may be computer devices such as a smart phone, a tablet computer, a notebook computer, and a desktop computer.
Fig. 3 is a flowchart of a specific method of a component standardization management method according to an embodiment of the present invention, where the method specifically includes steps S201 to S203.
S201: a component library is created.
In this step, the component library is a database for storing components, and in this embodiment, the component library stores the components in a key-value manner, where an id of the component is a key and the component is a value.
S202: receiving a to-be-processed component sent by a providing user side and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component.
In order to enable the access client to smoothly call the standard component, the interface is constructed in the component to be processed so that the access client can call the standard component, and the calling complexity of the standard component is greatly reduced.
And receiving the components to be processed through the communication connection established between the TCP or UDP and the providing user side.
It should be noted that TCP (Transmission Control Protocol) is a connection-oriented, reliable transport layer communication Protocol based on byte stream, and is defined by RFC 793 of IETF. In the simplified OSI model of computer networks, which performs the functions specified by the transport layer four, the User Datagram Protocol (UDP) is another important transport protocol within the same layer. In the Internet protocol suite (Internet protocol suite), the TCP layer is an intermediate layer located above the IP layer and below the application layer. Reliable, pipe-like connections are often required between the application layers of different hosts, but the IP layer does not provide such a flow mechanism, but rather provides unreliable packet switching. UDP is short for User Datagram Protocol, a Chinese name is User Datagram Protocol, and is a connectionless transport layer Protocol in OSI (Open System Interconnection) reference model, which provides transaction-oriented simple unreliable information transfer service, and IETF RFC 768 is a formal specification of UDP.
In a preferred embodiment, referring to fig. 4, the providing-side process includes:
a1: executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning the providing refusal information and ending.
To ensure that the received pending component belongs to an acceptable component that can be processed and run, it is therefore determined by the providing thread of authority whether the pending component is an acceptable component, i.e.: comparing the component to be processed with a preset provision authority list (which can be regarded as a white list) and judging whether the component is a processable component; and detecting whether the component to be processed can normally run or not, judging whether the component to be processed is a runnable component or not, and if the component to be processed has the characteristics of being processable and runnable simultaneously, judging the component to be processed as an acceptable component.
Specifically, referring to fig. 5, the permission providing thread includes:
a11: extracting a component code of a component to be processed, and judging whether the component code belongs to a preset provision authority list; wherein, the component code records the ID information of the providing user side;
a12: if yes, judging that the component to be processed is authorized;
a13: if not, returning the refusal providing information and ending;
a14: detecting whether the authorized component to be processed can normally run or not;
a15: if yes, judging the component to be processed to be an acceptable component;
a16: if not, returning the providing refusal information and ending.
A2: and executing the standardized thread to construct a Restful interface in the to-be-processed component to obtain a standard component.
In this step, the restful interface (presentation layer state transition) is an API interface of a design style and a development mode of a network application program, which is based on HTTP and may be defined using XML format or JSON format.
It should be noted that, due to the restful interface architecture style specification, the meta-operations of the data, i.e. CRUD (create, read, update and delete, i.e. the incremental and destructive modification of the data) operations, respectively correspond to the HTTP methods: GET is used for obtaining resources, POST is used for building resources (also can be used for updating resources), PUT is used for updating resources, DELETE is used for deleting resources, thus unifying interfaces of data operation, and completing all the work of adding, deleting, checking, modifying and obtaining resources of data only by an HTTP method; therefore, the restful interface only defines resource operation and does not participate in business logic, so that any user side can be directly based on http without any other protocol such as message protocol (for example, get/post/put/delete is CRUD operation), and since the restful interface is resource-oriented, self-explanatory and simple in data description (data exchange is generally performed by xml and json), when the restful interface (access and operation resources) is called, the context and the current state are not considered, and the complexity is greatly reduced.
A3: and sending the standard component to a preset component library.
By storing the standard components in the component library, the access user terminal can call the standard components quickly.
S203: receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal.
The standard component is called for ensuring an access user side with calling authority, or a standard module formed by assembling a plurality of standard components is called, so that the access user side can obtain reliable standard components or standard modules.
In a preferred embodiment, referring to fig. 6, the access terminal process includes:
b1: executing an access authority thread to judge whether the calling request has calling authority; if so, extracting the calling thread; if not, returning the calling refusal information.
In order to ensure that the received calling request has calling authority, the calling of the component by a user end without the authority is avoided, so that the safety of the component and a server where the component is located is ensured; this step judges whether the call request has the authority through the access authority thread, namely: the call request is compared with a preset access authority list (which can be regarded as a white list) to ensure that the call request for executing the call thread is authorized.
Specifically, referring to fig. 7, the access authority thread includes:
b11: extracting a calling code of the calling request, and judging whether the calling code belongs to a preset access authority list or not; the calling code records ID information of the access user terminal;
b12: if yes, judging that the calling request has a calling authority;
b13: if not, returning the providing refusal information and ending.
B2: executing a calling thread to obtain the standard component from the component library according to the calling request, and/or assembling the standard component to form a standard module.
In order to avoid the problem that the access user end needs to reprocess the obtained standard component to obtain a module for completing a complex task, so that the access user end uses the standard component complicatedly, the step obtains the standard component through a calling thread and/or forms the standard module which can be directly called by assembling the standard component, and convenience is provided for the access user end to use the standard component.
Specifically, referring to fig. 8, the calling thread includes:
b21: extracting the component ID in the calling request, and acquiring a standard component corresponding to the component ID from a component library;
b22: judging whether the number of the obtained standard components is one or not;
b23: if so, ending the calling thread;
b24: if not, extracting the incidence relation in the calling request, and assembling the standard component according to the incidence relation to obtain a standard module.
It should be noted that the association describes a calling relationship between components corresponding to component IDs in the calling request.
Illustratively, the component ID of the invocation request is extracted, such as: a005; the standard component corresponding to a005 is extracted and it is determined that the component ID of the call request is one, so the call thread is directly ended.
Illustratively, the component ID of the invocation request is extracted, such as: a005, a009, B010; extracting the standard components corresponding to the A005, the A009 and the B010, and judging that the component IDs of the calling requests are not one, so that the association relation in the calling requests is extracted;
assuming that the correlation is:
m1: calling A005 to operate data to be processed to obtain first data;
m2: calling B010 to operate the first data to obtain second data;
m3: and calling the A009 to operate the second data to obtain an operation result.
Then, the standard components corresponding to a005, a009 and B010 are assembled according to the association relationship, and the standard modules with the calling sequence of the standard component corresponding to a005, the standard component corresponding to B010 and the standard component corresponding to a009 are obtained.
B3: and executing a communication thread to enable the obtained standard component or the standard module to establish communication connection with the access client.
In this step, a standard component or a standard module is connected to the communication established by the access client through TCP or UDP. The access user terminal only needs to send the data to be processed to the server through the communication connection and calls the standard component or the standard module to calculate the data to obtain the calculation result, so that the standard component and the standard module do not need to be sent to the access user terminal, the data transmission pressure of the communication connection is greatly reduced, and the safety of the standard component and the standard module is also ensured.
It should be noted that TCP (Transmission Control Protocol) is a connection-oriented, reliable transport layer communication Protocol based on byte stream, and is defined by RFC 793 of IETF. In the simplified OSI model of computer networks, which performs the functions specified by the transport layer four, the User Datagram Protocol (UDP) is another important transport protocol within the same layer. In the Internet protocol suite (Internet protocol suite), the TCP layer is an intermediate layer located above the IP layer and below the application layer. Reliable, pipe-like connections are often required between the application layers of different hosts, but the IP layer does not provide such a flow mechanism, but rather provides unreliable packet switching. UDP is short for User Datagram Protocol, a Chinese name is User Datagram Protocol, and is a connectionless transport layer Protocol in OSI (Open System Interconnection) reference model, which provides transaction-oriented simple unreliable information transfer service, and IETF RFC 768 is a formal specification of UDP.
Example three:
referring to fig. 9, a device 1 for component standardization management of the present embodiment includes:
the providing end management module 12 is configured to receive a to-be-processed component sent by a providing user end and execute a providing end process, so as to construct an interface in the to-be-processed component to obtain a standard component;
the access terminal management module 13 is configured to receive a call request sent by an access terminal and execute an access terminal process, so as to obtain a standard component according to the call request sent by the access terminal, or assemble the standard component to form a standard module, and establish a communication connection between the standard component or the standard module and the access terminal.
Optionally, the component standardization management apparatus 1 further includes:
the creating module 11 is configured to create a component library, where the component library is a database used for storing components, and the component library stores the components in a key-value manner, where id of the component is key and the component is value.
The technical scheme is based on the development field of research and development management, and a standard component is obtained by constructing an interface in the component to be processed; according to a calling request sent by an access user terminal, a standard component is obtained according to the calling request, or the standard component is assembled to form a standard module, and communication connection is established between the standard component or the standard module and the access user terminal to obtain a module management tool which is used for assisting in developing the component and the module.
Example four:
in order to achieve the above object, the present invention further provides a computer device 5, in which components of the component standardization management apparatus 1 according to the third embodiment can be distributed in different computer devices, and the computer device 5 can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster formed by a plurality of servers) for executing programs, and the like. The computer device 5 of the present embodiment includes at least, but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in FIG. 10. It should be noted that fig. 10 only shows a computer device with components, but it should be understood that not all of the shown components are required to be implemented, and more or fewer components may be implemented instead.
In this embodiment, the memory 51 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the memory 51 may be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device. Of course, the memory 51 may also include both internal and external storage devices of the computer device. In this embodiment, the memory 51 is generally used for storing an operating system and various application software installed in the computer device, for example, a program code of the component standardization management apparatus in the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 52 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In this embodiment, the processor 52 is configured to run a program code stored in the memory 51 or process data, for example, run a component standardization management apparatus, so as to implement the component standardization management method of the first embodiment and the second embodiment.
Example five:
to achieve the above object, the present invention also provides a computer-readable storage medium including a storage data area storing data created according to use of a blockchain node and a storage program area storing a computer program; the program storage area includes a storage medium such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which implements a corresponding function when executed by the processor 52. The computer-readable storage medium of the present embodiment is used for storing a component standardization management apparatus, and when executed by the processor 52, implements the component standardization management method of the first embodiment and the second embodiment.
Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.
The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for standardized management of components, comprising:
receiving a to-be-processed component sent by a providing user side and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component;
receiving a calling request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establishing communication connection between the standard component or the standard module and the access user terminal.
2. The method for component standardized management according to claim 1, wherein before receiving the to-be-processed component sent by the providing client and executing the providing client process, the method comprises:
creating a component library for storing a database of components;
the component library stores the components in a key-value mode, wherein the id of each component is a key, and the component is a value.
3. The component standardization management method according to claim 1, wherein the providing-side process includes:
executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning the refusal providing information and ending;
executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component;
and sending the standard component to a preset component library.
4. The component standardization management method according to claim 3, wherein the providing of the authority thread includes:
extracting a component code of a component to be processed, and judging whether the component code belongs to a preset provision authority list; if yes, judging that the component to be processed is authorized; if not, returning the refusal providing information and ending; wherein, the component code records the ID information of the providing user side;
detecting whether the authorized component to be processed can normally run or not; if yes, judging the component to be processed to be an acceptable component; if not, returning the providing refusal information and ending.
5. The component standardized management method according to claim 1, wherein the access end process comprises:
executing an access authority thread to judge whether the calling request has calling authority; if so, extracting the calling thread; if not, returning calling rejection information;
executing a calling thread to obtain a standard component from a component library according to the calling request and/or assembling the standard component to form a standard module;
and executing a communication thread to enable the obtained standard component or the standard module to establish communication connection with the access client.
6. The component standardized management method according to claim 5, wherein the access authority thread comprises:
extracting a calling code of the calling request, and judging whether the calling code belongs to a preset access authority list or not; if yes, judging that the calling request has a calling authority; if not, returning the refusal providing information and ending; and the calling code records the ID information of the access user terminal.
7. The component standardization management method according to claim 5, wherein the calling thread includes:
extracting the component ID in the calling request, and acquiring a standard component corresponding to the component ID from a component library;
judging whether the number of the obtained standard components is one or not; if so, ending the calling thread; if not, extracting the incidence relation in the calling request, and assembling the standard component according to the incidence relation to obtain a standard module.
8. An apparatus for standardized management of components, comprising:
the system comprises a providing end management module, a providing end processing module and a standard component acquisition module, wherein the providing end management module is used for receiving a to-be-processed component sent by a providing user end and executing a providing end process so as to construct an interface in the to-be-processed component to obtain the standard component;
the access terminal management module is used for receiving a calling request sent by an access user terminal and executing an access terminal process so as to acquire a standard component according to the calling request sent by the access user terminal or assemble the standard component to form a standard module according to the calling request, and establish communication connection between the standard component or the standard module and the access user terminal.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the standardized management of components of any one of claims 1 to 7 are implemented by the processor of the computer device when the computer program is executed.
10. A computer-readable storage medium comprising a storage data area storing data created according to use of blockchain nodes and a storage program area storing a computer program, wherein the computer program stored in the storage medium implements the steps of the component standardized management method according to any one of claims 1 to 7 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852276.8A CN111984236A (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852276.8A CN111984236A (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111984236A true CN111984236A (en) | 2020-11-24 |
Family
ID=73442895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010852276.8A Pending CN111984236A (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111984236A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113934470A (en) * | 2021-10-19 | 2022-01-14 | 京东科技控股股份有限公司 | Method for constructing and using federated learning framework and related equipment |
| CN115826521A (en) * | 2022-11-22 | 2023-03-21 | 广州致远仪器有限公司 | Production process control method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030187915A1 (en) * | 2002-03-29 | 2003-10-02 | Xian-He Sun | Communication and process migration protocols for distributed heterogenous computing |
| CN109408232A (en) * | 2018-10-17 | 2019-03-01 | 山东易通发展集团有限公司 | A kind of modularization bus calling execution system based on transaction flow |
| CN109710214A (en) * | 2018-08-17 | 2019-05-03 | 深圳壹账通智能科技有限公司 | Construction method, device, terminal device and the storage medium of electronic signature software |
| CN110324376A (en) * | 2018-03-30 | 2019-10-11 | 江苏融成嘉益信息科技有限公司 | A kind of business micro services Component Gallery |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
| CN111142855A (en) * | 2020-04-03 | 2020-05-12 | 中邮消费金融有限公司 | Software development method and software development system |
| CN111324465A (en) * | 2020-02-19 | 2020-06-23 | 深圳壹账通智能科技有限公司 | Multithread calling method and device, computer system and storage medium |
-
2020
- 2020-08-21 CN CN202010852276.8A patent/CN111984236A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030187915A1 (en) * | 2002-03-29 | 2003-10-02 | Xian-He Sun | Communication and process migration protocols for distributed heterogenous computing |
| CN110324376A (en) * | 2018-03-30 | 2019-10-11 | 江苏融成嘉益信息科技有限公司 | A kind of business micro services Component Gallery |
| CN109710214A (en) * | 2018-08-17 | 2019-05-03 | 深圳壹账通智能科技有限公司 | Construction method, device, terminal device and the storage medium of electronic signature software |
| CN109408232A (en) * | 2018-10-17 | 2019-03-01 | 山东易通发展集团有限公司 | A kind of modularization bus calling execution system based on transaction flow |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
| CN111324465A (en) * | 2020-02-19 | 2020-06-23 | 深圳壹账通智能科技有限公司 | Multithread calling method and device, computer system and storage medium |
| CN111142855A (en) * | 2020-04-03 | 2020-05-12 | 中邮消费金融有限公司 | Software development method and software development system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113934470A (en) * | 2021-10-19 | 2022-01-14 | 京东科技控股股份有限公司 | Method for constructing and using federated learning framework and related equipment |
| CN115826521A (en) * | 2022-11-22 | 2023-03-21 | 广州致远仪器有限公司 | Production process control method and device, electronic equipment and storage medium |
| CN115826521B (en) * | 2022-11-22 | 2023-10-20 | 广州致远仪器有限公司 | Production process control method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111343168B (en) | Identity authentication method and device, computer equipment and readable storage medium | |
| CN112130871B (en) | Method and device for remotely deploying middleware, computer equipment and storage medium | |
| CN112714158B (en) | Transaction processing method, relay network, cross-link gateway, system, medium and equipment | |
| CN111984236A (en) | Component standardization management method and device, computer equipment and readable storage medium | |
| CN113641414A (en) | Internet of things equipment access method and device, computer equipment and storage medium | |
| US20210344766A1 (en) | Systems and methods for decentralization of blockchain-based processes employing a blockchain-associated front end or blockchain-associated user interface | |
| CN114124929A (en) | Cross-network data processing method and device | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| US8510707B1 (en) | Mainframe-based web service development accelerator | |
| CN111831365A (en) | Interface route forwarding method, system, computer equipment and readable storage medium | |
| CN113726770A (en) | Data interception method and device, computer equipment and storage medium | |
| CN111221511A (en) | Development system of plug-in type micro-service interface | |
| CN114610598A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| US8555239B1 (en) | Mainframe-based web service development accelerator | |
| CN109299173A (en) | Data transmission method, device and storage medium | |
| CN112559027A (en) | Method, system, device and readable storage medium for creating and managing functional components | |
| CN111314355B (en) | Authentication method, device, equipment and medium of VPN (virtual private network) server | |
| CN110908801A (en) | Data processing method and device based on block chain, computer equipment and storage medium | |
| CN115914319A (en) | Remote management method and system for virtual reality equipment | |
| CN114968822A (en) | Interface testing method and device, computer equipment and storage medium | |
| US8479175B1 (en) | Mainframe-based web service development accelerator | |
| CN115102769A (en) | SCADA system access authentication method, device, equipment and storage medium | |
| CN111447080B (en) | Private network decentralization control method, device and computer readable storage medium | |
| CN111310141B (en) | Authentication management method, device, computer equipment and storage medium | |
| CN114296880A (en) | Service request processing method, device, equipment and medium based on large-scale cluster |
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 |