CN111274051A - Data processing method and device, electronic equipment and computer readable storage medium - Google Patents
Data processing method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN111274051A CN111274051A CN202010060168.7A CN202010060168A CN111274051A CN 111274051 A CN111274051 A CN 111274051A CN 202010060168 A CN202010060168 A CN 202010060168A CN 111274051 A CN111274051 A CN 111274051A
- Authority
- CN
- China
- Prior art keywords
- data
- corresponding relation
- target data
- component
- hashmap
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a data processing method and device, electronic equipment and a computer readable storage medium. The method comprises the following steps: when data is requested through a data interface of the component, determining a first corresponding relation of the component and storing the first corresponding relation into a HashMap, wherein the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data; and acquiring target data from the Context based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data processing method and apparatus, an electronic device, and a computer-readable storage medium.
Background
The components are complete program modules for realizing specific functions, data interaction among the components can be realized through a Context (Context), and the components can acquire data with the same field names as the data interfaces of the components in the Context.
In actual use, data in the Context may have multiple sources, data of the same meaning from different sources may be set with different field names, and for some reusable components, the field names of the data interfaces may not be consistent with the field names of the data in the Context, which may cause the components to fail to obtain the data from the Context, and affect normal invocation of the components.
Disclosure of Invention
The present application aims to solve at least one of the above technical drawbacks. The technical scheme adopted by the application is as follows:
in a first aspect, an embodiment of the present application provides a data processing method, where the method includes:
when data is requested through a data interface of the component, determining a first corresponding relation of the component and storing the first corresponding relation into a HashMap, wherein the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data;
and acquiring target data from the Context based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data.
Optionally, the method further includes:
storing the return value in HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
Optionally, determining a first correspondence of the components comprises:
based on the component names of the components, acquiring a first corresponding relation from a pre-configured corresponding relation set, wherein the corresponding relation set comprises the corresponding relation between the interface fields of the components and the data names.
Optionally, the set of correspondences is stored in an XML configuration file.
In a second aspect, an embodiment of the present application provides an apparatus for processing data, where the apparatus includes:
the system comprises a corresponding relation acquisition module, a hash table hash map storage module and a data interface processing module, wherein the corresponding relation acquisition module is used for determining a first corresponding relation of a component and storing the first corresponding relation into the hash table hash map when data is requested through a data interface of the component, and the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data;
and the data processing module is used for acquiring the target data from the Context based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data.
Optionally, the apparatus further includes a return value processing module, configured to:
storing the return value in HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
Optionally, when determining the first corresponding relationship of the component, the corresponding relationship obtaining module is specifically configured to:
based on the component names of the components, acquiring a first corresponding relation from a pre-configured corresponding relation set, wherein the corresponding relation set comprises the corresponding relation between the interface fields of the components and the data names.
Optionally, the set of correspondences is stored in an XML configuration file.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory;
a memory for storing operating instructions;
a processor, configured to execute the processing method of the data as shown in any implementation manner of the first aspect of the present application by calling an operation instruction.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for processing data shown in any implementation manner of the first aspect of the present application.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
according to the scheme provided by the embodiment of the application, when data is requested through the data interface of the component, the corresponding relation between the field name of the data interface of the component and the field name of the target data is determined, the target data is obtained from the Context according to the field name of the target data and is stored in the HashMap, so that the component obtains the target data from the HashMap, and the target data is processed to determine the return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of a data processing method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Data of the same meaning in the Context may be set with different field names due to different sources or different service properties. For example, in the banking system, the field name corresponding to the client ID passed to the Context when the seller information is queried is sellcusto, and the field name corresponding to the client ID passed to the Context when the buyer information is queried is buycusto.
When the reusable component is called, the field name of the data interface of the component may be different from the field name of the data in the Context, which may result in the component not being able to obtain the data from the Context. For example, when the client information query component is called, the client ID needs to be acquired from the Context, the field name of the client information query component data interface is custo, and the field name corresponding to the client ID in the Context is selcustno or buyCustNo.
If the components are written separately for data of different field names in the Context, for example, the customer information query components are written separately for the vendor/vendor customer information query function, the reusability of the components is poor, and the code repeatability is high. If the components specially used for field name conversion are written according to different field names, a large number of field name conversion components for different services exist, and reusability is not available.
The embodiment of the application provides a data processing method and device, an electronic device and a computer-readable storage medium, which aim to solve at least one of the above technical problems in the prior art.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 shows a schematic flow diagram of a data processing method provided in an embodiment of the present application, and as shown in fig. 1, the method mainly includes:
step S110, when data is requested through a data interface of the component, determining a first corresponding relation of the component and storing the first corresponding relation into a HashMap (HashMap), wherein the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data;
and S120, acquiring target data from the Context (Context) based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data.
In the embodiment of the application, the component can be a reusable component, and when the component needs to be called to process target data, data can be requested through a data interface of the component.
In the embodiment of the present application, the first corresponding relationship may be determined, and the field name of the target data corresponding to the field name of the data interface of the component may be determined. After the first corresponding relationship is determined, the first corresponding relationship may be stored in a HashMap, and the target data may be obtained by the HashMap.
In the embodiment of the application, based on the first corresponding relationship, the field name of the target data can be obtained, based on the field name of the target data, the target data can be obtained from the Context, and the target data can be stored in the HashMap after the target data is obtained.
In the embodiment of the application, after the target data is stored in the HashMap, the component can acquire the target data from the HashMap and process the target data to obtain the return value of the target data.
According to the method provided by the embodiment of the application, when data is requested through the data interface of the component, the corresponding relation between the field name of the data interface of the component and the field name of the target data is determined, the target data is obtained from the Context according to the field name of the target data and is stored in the HashMap, so that the component obtains the target data from the HashMap, and the target data is processed to determine the return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
In an optional manner of the embodiment of the present application, the method further includes:
storing the return value in HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
In the embodiment of the application, after the target data is processed by the component, the return value can be obtained, and the return value has the same field name as the target data. In some service scenarios, it may be necessary for the return value to overwrite target data in the Context, and at this time, the return value may be stored in the Context to implement overwriting the target data. In other traffic scenarios, it may be necessary to keep the return value and the target data separately, and then the second correspondence may be preconfigured in order to avoid overwriting the target data. And storing the return value in HashMap, and after determining the second corresponding relation between the field name of the target data and the newly added field name, storing the return value in Context based on the newly added field name. Specifically, the field name of the return value may be changed to a new field and then stored in the Context.
In the embodiment of the application, the field name of the new field is inconsistent with the field name of the target data, so that the field name of the return value is changed into the new field and then stored in the Context, and the target data cannot be covered.
In an optional manner of the embodiment of the present application, determining the first corresponding relationship of the components includes:
based on the component names of the components, acquiring a first corresponding relation from a pre-configured corresponding relation set, wherein the corresponding relation set comprises the corresponding relation between the interface fields of the components and the data names.
In the embodiment of the application, the corresponding relations are configured for each component in the corresponding relation set, and when the first corresponding relation of the component is determined, the corresponding relation set can be traversed based on the component name to determine the first corresponding relation.
In actual use, the corresponding relationship set may be stored in an Extensible markup language (XML) configuration file. When the service is started, the corresponding relationship set in the configuration file may be stored in the memory in the form of XMLbean.
Based on the same principle as the method shown in fig. 1, fig. 2 shows a schematic structural diagram of a data processing apparatus provided in an embodiment of the present application, and as shown in fig. 2, the data processing apparatus 20 may include:
the corresponding relationship obtaining module 210 is configured to, when data is requested through a data interface of a component, determine a first corresponding relationship of the component and store the first corresponding relationship to a hash table HashMap, where the first corresponding relationship is a corresponding relationship between a field name of the data interface and a field name of target data;
and the data processing module 220 is configured to obtain the target data from the Context based on the first corresponding relationship and store the target data to the HashMap, so that the component obtains the target data from the HashMap and processes the target data to determine a return value of the target data.
According to the device provided by the embodiment of the application, when data is requested through the data interface of the component, the corresponding relation between the field name of the data interface of the component and the field name of the target data is determined, the target data is obtained from the Context according to the field name of the target data and is stored in the HashMap, so that the component obtains the target data from the HashMap, and the target data is processed to determine the return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
Optionally, the apparatus further includes a return value processing module, configured to:
storing the return value in HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
Optionally, when determining the first corresponding relationship of the component, the corresponding relationship obtaining module is specifically configured to:
based on the component names of the components, acquiring a first corresponding relation from a pre-configured corresponding relation set, wherein the corresponding relation set comprises the corresponding relation between the interface fields of the components and the data names.
Optionally, the set of correspondences is stored in an XML configuration file.
It is to be understood that the above modules of the data processing apparatus in the present embodiment have functions of implementing the corresponding steps of the data processing method in the embodiment shown in fig. 1. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The modules can be software and/or hardware, and each module can be implemented independently or by integrating a plurality of modules. For the functional description of each module of the data processing apparatus, reference may be specifically made to the corresponding description of the data processing method in the embodiment shown in fig. 1, and details are not repeated here.
The embodiment of the application provides an electronic device, which comprises a processor and a memory;
a memory for storing operating instructions;
and the processor is used for executing the data processing method provided by any embodiment of the application by calling the operation instruction.
As an example, fig. 3 shows a schematic structural diagram of an electronic device to which an embodiment of the present application is applicable, and as shown in fig. 3, the electronic device 2000 includes: a processor 2001 and a memory 2003. Wherein the processor 2001 is coupled to a memory 2003, such as via a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that the transceiver 2004 is not limited to one in practical applications, and the structure of the electronic device 2000 is not limited to the embodiment of the present application.
The processor 2001 is applied to the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter, and the transceiver 2004 is applied to the embodiments of the present application to implement the functions of the electronic device of the embodiments of the present application to communicate with other devices when executed.
The Processor 2001 may be a CPU (Central Processing Unit), general Processor, DSP (Digital Signal Processor), ASIC (Application specific integrated Circuit), FPGA (Field Programmable Gate Array) or other Programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 2001 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.
The Memory 2003 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically erasable programmable Read Only Memory), a CD-ROM (Compact disk Read Only Memory) or other optical disk storage, optical disk storage (including Compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.
Optionally, the memory 2003 is used for storing application program code for performing the disclosed aspects, and is controlled in execution by the processor 2001. The processor 2001 is configured to execute the application program code stored in the memory 2003 to implement the data processing method provided in any of the embodiments of the present application.
The electronic device provided by the embodiment of the application is applicable to any embodiment of the method, and is not described herein again.
Compared with the prior art, when data is requested through a data interface of a component, the corresponding relation between the field name of the data interface of the component and the field name of target data is determined, the target data is obtained from Context according to the field name of the target data and stored in HashMap, so that the component obtains the target data from the HashMap, and the target data is processed to determine the return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
The embodiment of the application provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium, and when the program is executed by a processor, the program realizes the processing method of the data shown in the above method embodiment.
The computer-readable storage medium provided in the embodiments of the present application is applicable to any of the embodiments of the foregoing method, and is not described herein again.
Compared with the prior art, when data is requested through a data interface of a component, the corresponding relation between the field name of the data interface of the component and the field name of target data is determined, the target data is obtained from Context according to the field name of the target data and stored to HashMap, so that the component obtains the target data from the HashMap, and the target data is processed to determine the return value of the target data. In the scheme, the corresponding relation between the field name of the data interface and the field name of the target data is determined, the target data is obtained in Context and stored to HashMap, so that the component obtains the target data from the HashMap, the data is obtained under the condition that the field name of the data interface is inconsistent with the field name of the data in the Context, the normal calling of the component to the data in the Context is ensured, and the multiplexing of the component is facilitated.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for processing data, comprising:
when data is requested through a data interface of a component, determining a first corresponding relation of the component and storing the first corresponding relation to a HashMap, wherein the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data;
and acquiring target data from the Context based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data.
2. The method of claim 1, further comprising:
storing the return value in the HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
3. The method of claim 1, wherein determining the first correspondence of the component comprises:
and acquiring a first corresponding relation from a pre-configured corresponding relation set based on the component name of the component, wherein the corresponding relation set comprises the corresponding relation between the interface field of each component and the data name.
4. The method according to any of claims 1-3, wherein the set of correspondences is stored in an extensible markup language (XML) configuration file.
5. An apparatus for processing data, comprising:
the system comprises a corresponding relation acquisition module, a data interface processing module and a data processing module, wherein the corresponding relation acquisition module is used for determining a first corresponding relation of a component and storing the first corresponding relation into a HashMap (HashMap) when data is requested through a data interface of the component, and the first corresponding relation is the corresponding relation between the field name of the data interface and the field name of target data;
and the data processing module is used for acquiring target data from Context based on the first corresponding relation and storing the target data to the HashMap, so that the component acquires the target data from the HashMap and processes the target data to determine a return value of the target data.
6. The apparatus of claim 5, further comprising a return value processing module to:
storing the return value in the HashMap;
and if the second corresponding relation between the field name of the target data and the newly added field name exists in the HashMap, storing the return value in the Context based on the newly added field name.
7. The apparatus according to claim 5, wherein the correspondence obtaining module, when determining the first correspondence of the component, is specifically configured to:
and acquiring a first corresponding relation from a pre-configured corresponding relation set based on the component name of the component, wherein the corresponding relation set comprises the corresponding relation between the interface field of each component and the data name.
8. The apparatus according to any of claims 5-7, wherein the set of correspondences is stored in an XML configuration file.
9. An electronic device comprising a processor and a memory;
the memory is used for storing operation instructions;
the processor is used for executing the method of any one of claims 1-4 by calling the operation instruction.
10. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010060168.7A CN111274051B (en) | 2020-01-19 | 2020-01-19 | Data processing method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010060168.7A CN111274051B (en) | 2020-01-19 | 2020-01-19 | Data processing method and device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111274051A true CN111274051A (en) | 2020-06-12 |
| CN111274051B CN111274051B (en) | 2023-08-22 |
Family
ID=70997483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010060168.7A Active CN111274051B (en) | 2020-01-19 | 2020-01-19 | Data processing method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111274051B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080082535A1 (en) * | 2006-09-29 | 2008-04-03 | Sven-Eric Eigemann | Method and system for automatically generating a communication interface |
| CN101655806A (en) * | 2009-09-25 | 2010-02-24 | 马丰文 | Interaction method of software system build-in component data |
| CN102567400A (en) * | 2010-12-31 | 2012-07-11 | 阿里巴巴集团控股有限公司 | Method for realizing Web visit and Web server |
| CN103235820A (en) * | 2013-04-27 | 2013-08-07 | 北京搜狐新媒体信息技术有限公司 | Data storage method and device in cluster system |
| US20150293958A1 (en) * | 2014-04-10 | 2015-10-15 | Facebook, Inc. | Scalable data structures |
| CN106569929A (en) * | 2016-10-26 | 2017-04-19 | 珠海许继芝电网自动化有限公司 | Real-time data access method and system for monitoring system |
| CN108776587A (en) * | 2018-05-25 | 2018-11-09 | 平安科技（深圳）有限公司 | Data capture method, device, computer equipment and storage medium |
| CN109144633A (en) * | 2018-07-20 | 2019-01-04 | 武汉斗鱼网络科技有限公司 | Data sharing method, device, equipment and the storage medium of active window |
| CN109254858A (en) * | 2018-08-31 | 2019-01-22 | 武汉斗鱼网络科技有限公司 | Data sharing method, device, equipment and the storage medium of active window |
| CN109388654A (en) * | 2017-08-04 | 2019-02-26 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for inquiring tables of data |
| CN109634996A (en) * | 2018-10-25 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Customer information table generating method, device, equipment and computer readable storage medium |
| CN110018998A (en) * | 2019-04-12 | 2019-07-16 | 深信服科技股份有限公司 | A kind of file management method, system and electronic equipment and storage medium |
| CN110515943A (en) * | 2019-07-30 | 2019-11-29 | 恩亿科(北京)数据科技有限公司 | Data storage, querying method and equipment, data processing equipment, storage medium |
-
2020
- 2020-01-19 CN CN202010060168.7A patent/CN111274051B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080082535A1 (en) * | 2006-09-29 | 2008-04-03 | Sven-Eric Eigemann | Method and system for automatically generating a communication interface |
| CN101655806A (en) * | 2009-09-25 | 2010-02-24 | 马丰文 | Interaction method of software system build-in component data |
| CN102567400A (en) * | 2010-12-31 | 2012-07-11 | 阿里巴巴集团控股有限公司 | Method for realizing Web visit and Web server |
| CN103235820A (en) * | 2013-04-27 | 2013-08-07 | 北京搜狐新媒体信息技术有限公司 | Data storage method and device in cluster system |
| US20150293958A1 (en) * | 2014-04-10 | 2015-10-15 | Facebook, Inc. | Scalable data structures |
| CN106569929A (en) * | 2016-10-26 | 2017-04-19 | 珠海许继芝电网自动化有限公司 | Real-time data access method and system for monitoring system |
| CN109388654A (en) * | 2017-08-04 | 2019-02-26 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for inquiring tables of data |
| CN108776587A (en) * | 2018-05-25 | 2018-11-09 | 平安科技（深圳）有限公司 | Data capture method, device, computer equipment and storage medium |
| CN109144633A (en) * | 2018-07-20 | 2019-01-04 | 武汉斗鱼网络科技有限公司 | Data sharing method, device, equipment and the storage medium of active window |
| CN109254858A (en) * | 2018-08-31 | 2019-01-22 | 武汉斗鱼网络科技有限公司 | Data sharing method, device, equipment and the storage medium of active window |
| CN109634996A (en) * | 2018-10-25 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Customer information table generating method, device, equipment and computer readable storage medium |
| CN110018998A (en) * | 2019-04-12 | 2019-07-16 | 深信服科技股份有限公司 | A kind of file management method, system and electronic equipment and storage medium |
| CN110515943A (en) * | 2019-07-30 | 2019-11-29 | 恩亿科(北京)数据科技有限公司 | Data storage, querying method and equipment, data processing equipment, storage medium |
Non-Patent Citations (3)
| Title |
|---|
| JIRI SEBEK, 等: "AOP-Based Approach for Local Data Management in Adaptive Interfaces", 《2016 6TH INTERNATIONAL CONFERENCE ON IT CONVERGENCE AND SECURITY(ICITCS)》, pages 1 - 5 * |
| OMAR ALAM, 等: "《Modeling a family of system for crisis management with concern-oriented reuse》", 《SOFTWARE: PRACTICE AND EXPERIENCE》, vol. 47, no. 7, pages 985 - 999 * |
| 马超: "基于可重用组件的海量文本数据处理工具的设计与实现", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 11, pages 138 - 630 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111274051B (en) | 2023-08-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110162544B (en) | Heterogeneous data source data acquisition method and device | |
| CN112182036A (en) | Data sending and writing method and device, electronic equipment and readable storage medium | |
| CN110601880A (en) | Cloud platform, service processing method, command interface and computer equipment | |
| CN110955715A (en) | ERP system, data conversion method and device of target platform and electronic equipment | |
| CN112861501A (en) | Report generation method and device, electronic equipment and computer readable storage medium | |
| CN109062906B (en) | Translation method and device for program language resources | |
| CN111949513A (en) | Configuration file loading method and device, electronic equipment and readable storage device | |
| CN112860802B (en) | Database operation statement processing method and device and electronic equipment | |
| CN107908565B (en) | Test method and test equipment | |
| CN109271180B (en) | Data processing method and device | |
| CN111274051B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN112181479A (en) | Method and device for determining difference between code file versions and electronic equipment | |
| CN112199272A (en) | Intelligent terminal testing method and device, terminal equipment and medium | |
| CN111324906A (en) | Automatic access method and device based on data interface and electronic equipment | |
| CN112738181A (en) | Method, device and server for cluster external IP access | |
| CN111639936A (en) | Transaction information acquisition method and device, electronic equipment and readable storage medium | |
| CN110688430A (en) | Method and device for obtaining data bypass and electronic equipment | |
| CN112650682B (en) | Page test processing method and device, electronic equipment and readable storage medium | |
| CN113741956B (en) | Method and device for transplanting version management function, version management method and device | |
| CN111666593B (en) | Electronic signature method, electronic signature device, electronic equipment and computer readable storage medium | |
| CN109377177B (en) | Flow processing method, device, equipment and computer readable storage medium | |
| CN112181837A (en) | Information processing method, information processing device and terminal equipment | |
| CN117539942A (en) | Information item conversion method, system, equipment and medium | |
| CN116257673A (en) | Data query method, device, equipment and storage medium based on elastic search | |
| CN106874408B (en) | Html information input method supporting various browser kernels |
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 |