CN111427614B - File version management method and device - Google Patents
File version management method and device Download PDFInfo
- Publication number
- CN111427614B CN111427614B CN202010199387.3A CN202010199387A CN111427614B CN 111427614 B CN111427614 B CN 111427614B CN 202010199387 A CN202010199387 A CN 202010199387A CN 111427614 B CN111427614 B CN 111427614B
- Authority
- CN
- China
- Prior art keywords
- file
- new version
- ipns
- ipfs
- pointer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- 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
Abstract
The application provides a file version management method and a device, wherein the method comprises the following steps: constructing a decentralised naming IPNS system, wherein the IPNS system comprises a plurality of IPFS nodes; after obtaining a new version file, storing the new version file to an IPFS node; pointing a file pointer of the IPNS system to a new version file of the IPFS node; and downloading the new version file based on the file pointer of the IPNS system. The application can realize file version management, has high downloading speed and high file tracking and displaying speed.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for managing a file version.
Background
Currently, in the prior art, a ClearCase tool (such as a banking system) is often adopted for version management, and the version management tool is relatively fast in updating files and operating speed under the condition of small number of files and small number of login people. For large-scale software development, the development mode of multi-person cooperation, the update downloading and tracing of the software version, the ClearCase tool has the defects of low downloading speed, slow file tracing, time consumption for displaying an operation tree and the like. In addition, limited by the server capacity, when the source code and execution version storage capacity of the project exceeds the machine capacity, the server will not exist once it is down. These are mainly due to the adoption of a centralized architecture in the version store process.
Disclosure of Invention
The embodiment of the application provides a file version management method, which is used for realizing file version management, and has the advantages of high downloading speed and high file tracking and displaying speed, and the method comprises the following steps:
constructing a decentralised naming IPNS system, wherein the IPNS system comprises a plurality of IPFS nodes;
after obtaining a new version file, storing the new version file to an IPFS node;
pointing a file pointer of the IPNS system to a new version file of the IPFS node;
and downloading the new version file based on the file pointer of the IPNS system.
The embodiment of the application provides a file version management device, which is used for realizing file version management, has high downloading speed and high file tracking and displaying speed, and comprises the following components:
the IPNS system construction module is used for constructing a decentralised naming IPNS system which comprises a plurality of IPFS nodes;
the storage module is used for storing the new version file to an IPFS node after the new version file is obtained;
the pointing module is used for pointing the file pointer of the IPNS system to the new version file of the IPFS node;
and the downloading module is used for downloading the new version file based on the file pointer of the IPNS system.
The embodiment of the application also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the file version management method when executing the computer program.
The embodiment of the application also provides a computer readable storage medium, which stores a computer program for executing the file version management method.
In the embodiment of the application, a decentralised naming IPNS system is constructed, wherein the IPNS system comprises a plurality of IPFS nodes; after obtaining a new version file, storing the new version file to an IPFS node; pointing a file pointer of the IPNS system to a new version file of the IPFS node; and downloading the new version file based on the file pointer of the IPNS system. In the above process, after the new version file is obtained, the new version file is stored in an IPFS node, and the file pointer of the IPNS system points to the new version file of the IPFS node, so that the new version file can be downloaded based on the file pointer of the IPNS system, and for the version management systems such as ClearCase tool, the file downloading speed, tracking speed and display speed are improved because different version files can be stored in a plurality of IPFS nodes. In addition, in the version development process, all version files are stored in the IPFS node in a distributed mode, and quick access and permanent storage of the version files are realized.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a flow chart of a file version management method according to an embodiment of the present application;
FIG. 2 is a detailed flowchart of a report data query method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a file version management apparatus according to an embodiment of the present application;
fig. 4 is a schematic diagram of a computer device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present application and their descriptions herein are for the purpose of explaining the present application, but are not to be construed as limiting the application.
In the description of the present specification, the terms "comprising," "including," "having," "containing," and the like are open-ended terms, meaning including, but not limited to. The description of the reference terms "one embodiment," "a particular embodiment," "some embodiments," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The order of steps involved in the embodiments is illustrative of the practice of the application, and is not limited and may be suitably modified as desired.
FIG. 1 is a flowchart of a file version management method according to an embodiment of the present application, as shown in FIG. 1, the method includes:
step 101, constructing a decentralised naming IPNS system, wherein the IPNS system comprises a plurality of IPFS nodes;
step 102, after obtaining a new version file, storing the new version file to an IPFS node;
step 103, pointing the file pointer of the IPNS system to the new version file of the IPFS node;
step 104, based on the file pointer of the IPNS system, downloading the new version file.
In the embodiment of the application, after the new version file is obtained, the new version file is stored in an IPFS node, and the file pointer of the IPNS system points to the new version file of the IPFS node, so that the new version file can be downloaded based on the file pointer of the IPNS system, and for the version management systems such as a ClearCase tool, and the like, the file downloading speed, the tracking speed and the display speed are improved because different version files can be stored on a plurality of IPFS nodes. In addition, in the version development process, all version files are stored in the IPFS node in a distributed mode, and quick access and permanent storage of the version files are realized.
In particular, in step 101, a de-centralized naming IPNS system is constructed, where the IPNS system includes a plurality of IPFS nodes, and the IPFS (Inter Planetary File System, interstellar file system) is a global-oriented, point-to-point distributed version of the file system, and the goal is to supplement (even replace) the hypertext transfer protocol (HTTP) currently governing the internet, connect all computing devices with the same file system together, and replace the domain name-based address by a content-based address, that is, the content that the user finds not an address but is stored somewhere, without verifying the identity of the sender, but only verifying the hash of the content, so that the web page can be faster, safer, more robust, and more durable. IPFS is a point-to-point distributed file system that connects computing devices all having the same file management mode.
The working principle of IPFS is as follows:
each file and all blocks therein have a cryptographically hashed hash value that uniquely identifies the file.
The IPFS can perform redundant file deletion for files having the same hash value, while keeping track of the history version record of each file.
The file searching mode in the IPFS is to search through the hash value of the file, and the node stored in the file and the file information related to the node can be determined through the hash value.
The IPNS system can realize that the file name is easy to read, and the file is not read through the hash value. The IPNS system is constructed by installing a plurality of IPFS nodes, one IPFS node can be installed on each application terminal, the IPNS system formed by the plurality of IPFS nodes is a private network, and the IPFS node installation process is as follows:
double clicking the ipfs.exe file, running once, and successfully installing the IPFS node.
The IPFS node is initialized through the IPFS init command line.
The execution command IPFS daemon starts the IPFS node and joins it to the IPNS system network.
In one implementation, the storing of the new version file to an IPFS node includes:
and storing the new version file to an IPFS node, and generating a hash value corresponding to the new version file.
In the above embodiment, in an IPNS system formed by a plurality of IPFS nodes, it may be determined to store the new version file to the IPFS node with larger free space by detecting which IPFS node has larger free space, and simultaneously generate a hash value corresponding to the new version file, for example, one hash value may be expressed as Qmsdafsdfasdf2314324112ksjsf3241 jksafjp 5vz5BVuvEgR.
In one embodiment, pointing the file pointer of the IPNS system to the new version file of the IPFS node includes:
and pointing the file pointer of the IPNS to the hash value corresponding to the new version file of the IPFS node.
In the above embodiment, the constant file constant.java in java needs to be modified, and the file is one of new version files and stored on the IPFS node, and after modification, the file is restored on the IPFS node.
The content of the current constans.java file is as follows:
when the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node, firstly, the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node by using the IPFS publishing command, and mapping of the file pointer of the IPNS and the hash value corresponding to the new version file is completed, wherein the code is as follows:
Ipfs name publish–key QmsdafsdfaG83ShsfsdfaH324112ksjsf3241jksafjjP5vz5BVuvEgR/ipfs/Qmsdafsdfasdf2314324112ksjsf3241jksafjjP5vz5BVuvEgR。
the above QmsdafsdfaG83 SsfscdfaH 324112ksjsf3241 jksafjP 5vz5BVuvEgR is a hash value.
Then, the constant. Java is modified (where the underlined part is the newly added part), and reloaded into the IPFS.
The modified constant.java file content is as follows:
in the process, the IPFS node ID is adopted by default to map the hash value of the new version file, and key value generation is added in the mapping process. The Key value is a Key value uniquely identifying the mapping of the IPFS node ID and the hash value of the new version file, and is generated as follows:
ipfs key gen--type＝rsa--size＝2048another
in one embodiment, the downloading of the new version file based on the file pointer of the IPNS system includes:
obtaining an address corresponding to a file pointer of the IPNS system;
and downloading the new version file based on the address.
In the above embodiment, for example, the address corresponding to the file pointer of the IPNS system corresponding to the hash value of QmsdafsdfaG83 shsfdfah 324112ksjsf3241 jksafjp 5vz5BVuvEgR is as follows:
file download was performed using http://127.0.0.1:8080/ipns/QmsdafsdfaG83 SsfscdfaH 324112ksjsf3241 jksafjp 5vz5BV uvEgR.
And downloading the new version file through the address.
In addition to file downloads, file version views may be performed and commands ipfs resolve address may be employed.
For example, when the address is as follows, the command to make a file version check is: ipfs resolve/ipns/QmsdafsdfaG83 shsfdfafa h324112ksjsf3241 jksafjp 5vz5BVuvEgR:
Ipns/QmsdafsdfaG83 SsfsdfaH 324112ksjsf3241 jksafjP 5vz5BVuvEgR.
The IPNS can provide mapping for the dynamic content of the ipfs, and a user can finally access different content of the ipfs file by accessing the fixed IPNS address through public operation.
The present application proposes the following embodiment to explain the detailed flow of the file version management method, fig. 2 is a detailed flow chart of the report data query method according to the embodiment of the present application, as shown in fig. 2, including:
step 201, constructing a decentralised naming IPNS system, wherein the IPNS system comprises a plurality of IPFS nodes;
step 202, after obtaining a new version file, storing the new version file to an IPFS node, and generating a hash value corresponding to the new version file;
step 203, pointing the file pointer of the IPNS to the hash value corresponding to the new version file of the IPFS node;
step 204, obtaining an address corresponding to a file pointer of the IPNS system;
and step 205, downloading the new version file based on the address.
Of course, it is to be understood that other variations of the above detailed procedures are also possible, and all related variations should fall within the protection scope of the present application.
In summary, in the method provided by the embodiment of the present application, a de-centralized naming IPNS system is constructed, where the IPNS system includes a plurality of IPFS nodes; after obtaining a new version file, storing the new version file to an IPFS node; pointing a file pointer of the IPNS system to a new version file of the IPFS node; and downloading the new version file based on the file pointer of the IPNS system. In the above process, after the new version file is obtained, the new version file is stored in an IPFS node, and the file pointer of the IPNS system points to the new version file of the IPFS node, so that the new version file can be downloaded based on the file pointer of the IPNS system, and for the version management systems such as ClearCase tool, the file downloading speed, tracking speed and display speed are improved because different version files can be stored in a plurality of IPFS nodes. In addition, in the version development process, all version files are stored in the IPFS node in a distributed mode, and quick access and permanent storage of the version files are realized. In addition, the method effectively solves the problem of searching the historical version through the IPNS, and the historical version can be permanently stored in the IPFS system without being limited by a central server. By establishing the file system network of the IPNS system, the disk space of the developer computer is fully utilized. The method stores the ideas of decentralization and can be applied to various management tools of version control.
The embodiment of the application also provides a file version management device, the principle of which is similar to that of a file version management method, and the description is omitted here.
FIG. 3 is a schematic diagram of a file version management apparatus according to an embodiment of the present application, as shown in FIG. 3, the apparatus includes:
an IPNS system construction module 301, configured to construct a decentralised naming IPNS system, where the IPNS system includes a plurality of IPFS nodes;
the storage module 302 is configured to store the new version file to an IPFS node after obtaining the new version file;
a pointing module 303, configured to point a file pointer of the IPNS system to a new version file of the IPFS node;
the downloading module 304 is configured to download the new version file based on the file pointer of the IPNS system.
In one embodiment, the storage module 302 is specifically configured to:
and storing the new version file to an IPFS node, and generating a hash value corresponding to the new version file.
In one embodiment, the pointing module 303 is specifically configured to:
and pointing the file pointer of the IPNS to the hash value corresponding to the new version file of the IPFS node.
In one embodiment, the download module 304 is specifically configured to:
obtaining an address corresponding to a file pointer of the IPNS system;
and downloading the new version file based on the address.
In summary, in the device provided by the embodiment of the present application, a de-centralized naming IPNS system is constructed, where the IPNS system includes a plurality of IPFS nodes; after obtaining a new version file, storing the new version file to an IPFS node; pointing a file pointer of the IPNS system to a new version file of the IPFS node; and downloading the new version file based on the file pointer of the IPNS system. In the above process, after the new version file is obtained, the new version file is stored in an IPFS node, and the file pointer of the IPNS system points to the new version file of the IPFS node, so that the new version file can be downloaded based on the file pointer of the IPNS system, and for the version management systems such as ClearCase tool, the file downloading speed, tracking speed and display speed are improved because different version files can be stored in a plurality of IPFS nodes. In addition, in the version development process, all version files are stored in the IPFS node in a distributed mode, and quick access and permanent storage of the version files are realized. In addition, the method effectively solves the problem of searching the historical version through the IPNS, and the historical version can be permanently stored in the IPFS system without being limited by a central server. By establishing the file system network of the IPNS system, the disk space of the developer computer is fully utilized. The method stores the ideas of decentralization and can be applied to various management tools of version control.
An embodiment of the present application further provides a computer device, and fig. 4 is a schematic diagram of the computer device in the embodiment of the present application, where the computer device can implement all steps in the file version management method in the foregoing embodiment, and the electronic device specifically includes the following contents:
a processor (processor) 401, a memory (memory) 402, a communication interface (Communications Interface) 403, and a bus 404;
wherein, the processor 401, the memory 402, and the communication interface 403 complete the communication with each other through the bus 404; the communication interface 403 is configured to implement information transmission between related devices such as a server device, a detection device, and a user device;
the processor 401 is configured to invoke a computer program in the memory 402, where the processor executes the computer program to implement all the steps in the file version management method in the above embodiment.
The embodiment of the application also provides a computer readable storage medium, which can realize all the steps of the report data query method in the embodiment, and the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program realizes all the steps of the file version management method in the embodiment.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the application, and is not meant to limit the scope of the application, but to limit the application to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the application are intended to be included within the scope of the application.
Claims (6)
1. A method for managing version of a file, comprising:
constructing a decentralised naming IPNS system, wherein the IPNS system comprises a plurality of IPFS nodes;
after obtaining a new version file, storing the new version file to an IPFS node;
pointing a file pointer of the IPNS system to a new version file of the IPFS node;
downloading the new version file based on the file pointer of the IPNS system;
storing the new version file to an IPFS node, comprising: storing the new version file to an IPFS node, and generating a hash value corresponding to the new version file;
the constant file constant.java in java needs to be modified, the constant file is one of new version files and is stored on the IPFS node, and the constant file is restored to the IPFS node after being modified;
directing the file pointer of the IPNS system to the new version file of the IPFS node comprises: the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node;
when the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node, the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node by using the IPFS publishing command, and mapping of the file pointer of the IPNS and the hash value corresponding to the new version file is completed; and modifying constant.java, and reloading the modified constant.java into the IPFS.
2. The file version management method according to claim 1, wherein the downloading of the new version file based on the file pointer of the IPNS system comprises:
obtaining an address corresponding to a file pointer of the IPNS system;
and downloading the new version file based on the address.
3. A file version management apparatus, comprising:
the IPNS system construction module is used for constructing a decentralised naming IPNS system which comprises a plurality of IPFS nodes;
the storage module is used for storing the new version file to an IPFS node after the new version file is obtained;
the pointing module is used for pointing the file pointer of the IPNS system to the new version file of the IPFS node;
the downloading module is used for downloading the new version file based on the file pointer of the IPNS system;
the storage module is specifically used for: storing the new version file to an IPFS node, and generating a hash value corresponding to the new version file;
the constant file constant.java in java needs to be modified, the constant file is one of new version files and is stored on the IPFS node, and the constant file is restored to the IPFS node after being modified;
the pointing module is specifically used for: the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node;
when the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node, the file pointer of the IPNS points to the hash value corresponding to the new version file of the IPFS node by using the IPFS publishing command, and mapping of the file pointer of the IPNS and the hash value corresponding to the new version file is completed; and modifying constant.java, and reloading the modified constant.java into the IPFS.
4. The file version management apparatus of claim 3 wherein the download module is specifically configured to:
obtaining an address corresponding to a file pointer of the IPNS system;
and downloading the new version file based on the address.
5. 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 processor implements the method of any of claims 1 to 2 when executing the computer program.
6. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program for executing the method of any one of claims 1 to 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010199387.3A CN111427614B (en) | 2020-03-20 | 2020-03-20 | File version management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010199387.3A CN111427614B (en) | 2020-03-20 | 2020-03-20 | File version management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111427614A CN111427614A (en) | 2020-07-17 |
| CN111427614B true CN111427614B (en) | 2023-08-22 |
Family
ID=71549678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010199387.3A Active CN111427614B (en) | 2020-03-20 | 2020-03-20 | File version management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427614B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104679782A (en) * | 2013-11-30 | 2015-06-03 | 鸿富锦精密工业（深圳）有限公司 | File version control system and method |
| CN109784058A (en) * | 2019-01-07 | 2019-05-21 | 中国银行股份有限公司 | Version strong consistency method of calibration, client, server and storage medium |
| CN110109874A (en) * | 2019-05-13 | 2019-08-09 | 北京共识数信科技有限公司 | A kind of non-stop layer distributed document retrieval method based on block chain |
| CN110244573A (en) * | 2019-06-27 | 2019-09-17 | 深圳市星际无限科技有限公司 | Storage system and intelligent appliance based on intelligent appliance |
| CN110263035A (en) * | 2019-05-31 | 2019-09-20 | 阿里巴巴集团控股有限公司 | Data storage, querying method and device and electronic equipment based on block chain |
| CN110597764A (en) * | 2019-10-10 | 2019-12-20 | 深圳前海微众银行股份有限公司 | File management method and device |
-
2020
- 2020-03-20 CN CN202010199387.3A patent/CN111427614B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104679782A (en) * | 2013-11-30 | 2015-06-03 | 鸿富锦精密工业（深圳）有限公司 | File version control system and method |
| CN109784058A (en) * | 2019-01-07 | 2019-05-21 | 中国银行股份有限公司 | Version strong consistency method of calibration, client, server and storage medium |
| CN110109874A (en) * | 2019-05-13 | 2019-08-09 | 北京共识数信科技有限公司 | A kind of non-stop layer distributed document retrieval method based on block chain |
| CN110263035A (en) * | 2019-05-31 | 2019-09-20 | 阿里巴巴集团控股有限公司 | Data storage, querying method and device and electronic equipment based on block chain |
| CN110244573A (en) * | 2019-06-27 | 2019-09-17 | 深圳市星际无限科技有限公司 | Storage system and intelligent appliance based on intelligent appliance |
| CN110597764A (en) * | 2019-10-10 | 2019-12-20 | 深圳前海微众银行股份有限公司 | File management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111427614A (en) | 2020-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107577427B (en) | data migration method, device and storage medium for blockchain system | |
| US10812566B2 (en) | Distributed steam processing | |
| CN107562513B (en) | Intelligent contract life cycle management method based on JAVA | |
| CN110334297B (en) | Terminal page loading method, terminal, server and storage medium | |
| EP3014479B1 (en) | Omega names: name generation and derivation | |
| CN103649945B (en) | Automatic synchronization of most recently used document lists | |
| CN109391509A (en) | A kind of method, system and the application server of more new application | |
| CN105512324B (en) | A kind of front-end module loader of packaging file local updating | |
| US20110320394A1 (en) | Creation and Revision of Network Object Graph Topology for a Network Performance Management System | |
| EP4099154A1 (en) | Shared software libraries for computing devices | |
| CN104423961B (en) | A kind of method and system for generating test script | |
| US20140059094A1 (en) | Making use of a file path to determine file locality for applications | |
| US20160140141A1 (en) | File lookup in a distributed file system | |
| CN110020272B (en) | Caching method and device and computer storage medium | |
| CN103369002A (en) | A resource downloading method and system | |
| CN110780918B (en) | Middleware container processing method and device, electronic equipment and storage medium | |
| CN115421764A (en) | Method, device, equipment and storage medium for identifying module to be upgraded | |
| CN111427614B (en) | File version management method and device | |
| US20230315405A1 (en) | Discovering matching code segments according to index and comparative similarity | |
| CN112463808A (en) | Data processing method and device of target cluster and server | |
| CN111782244A (en) | Configuration file updating method and device, computer equipment and storage medium | |
| CN116560716A (en) | APP construction method, device, equipment and storage medium | |
| CN112003736B (en) | Multi-node configuration information determining method, device and storage medium | |
| CN111563083B (en) | Report data query method, device and system | |
| US11809992B1 (en) | Applying compression profiles across similar neural network architectures |
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 |