CN112148350A - Remote version management method for works, electronic device and computer storage medium - Google Patents
Remote version management method for works, electronic device and computer storage medium Download PDFInfo
- Publication number
- CN112148350A CN112148350A CN202010924217.7A CN202010924217A CN112148350A CN 112148350 A CN112148350 A CN 112148350A CN 202010924217 A CN202010924217 A CN 202010924217A CN 112148350 A CN112148350 A CN 112148350A
- Authority
- CN
- China
- Prior art keywords
- data
- version
- remote
- file
- data files
- 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 31
- 230000005540 biological transmission Effects 0.000 claims abstract description 17
- 238000000034 method Methods 0.000 claims description 25
- 238000004364 calculation method Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 4
- 238000005538 encapsulation Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect 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/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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T13/00—Animation
Abstract
The application discloses a remote version management method of works, electronic equipment and a computer storage medium, wherein the remote version management method of the works comprises the following steps: dividing local version data of the work into a plurality of data files and sequentially sending the data files to a Git server, wherein the plurality of data files comprise version recording files; receiving file identification numbers corresponding to the plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files; and when the version record file identification number corresponding to the version record file is received, generating remote version information according to the version record file identification number. According to the technical scheme, a remote version management function is provided for the animation programming software, a user can share works conveniently, and the fault tolerance rate of data transmission can be effectively improved by a single data file transmission mode.
Description
Technical Field
The present application relates to the field of animation programming software development technologies, and in particular, to a method for managing remote versions of works, an electronic device, and a computer storage medium.
Background
As computer technology has developed, more and more people have begun to learn programming. Aiming at children, some programming interest enthusiasts and beginners, a plurality of simple and easy-to-learn animation programming software appear in the market, the threshold for learning of works manufactured by the animation programming software is low, and the software is simple to operate and high in interestingness.
The process of making the works by the animation programming software is long and staged, a user may save a plurality of versions locally after editing the versions for a plurality of times, the latest version data also needs to be uploaded to a cloud end to be shared with other users, the general animation programming software directly packs and encapsulates the version data of the works and then sends an encapsulation package to the cloud end for remote storage, but the mode of sending the version data in the form of the encapsulation package has large data transmission quantity and easily causes the problem of low transmission fault tolerance.
Disclosure of Invention
In order to solve the technical problem, the application provides a work remote version management method, an electronic device and a computer storage medium.
In a first aspect, the present application provides a method for remote version management of a work, where the method for remote version management of a work includes:
dividing local version data of the work into a plurality of data files, and sequentially sending the data files to a Git server, wherein the data files comprise version record files;
receiving file identification numbers corresponding to a plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files;
and when receiving the version record file identification number corresponding to the version record file, generating remote version information according to the version record file identification number.
In a second aspect, the present application provides an electronic device comprising a memory, a processor and program data stored on the memory and executable on the processor, wherein the processor executes the program data to implement the steps of the method for remote version management of a work as described above.
In a third aspect, the present application is directed to a computer storage medium for storing program data which, when executed by a processor, is configured to implement the steps of the remote version management method for a work as described above.
Different from the prior art, the method of the application comprises the following steps: dividing local version data of the work into a plurality of data files and sequentially sending the data files to a Git server, wherein the plurality of data files comprise version recording files; receiving file identification numbers corresponding to the plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files; and when the version record file identification number corresponding to the version record file is received, generating remote version information according to the version record file identification number. According to the technical scheme, a remote version management function is provided for the animation programming software, a user can share works conveniently, and the fault tolerance rate of data transmission can be effectively improved by a single data file transmission mode.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic flow chart diagram illustrating an embodiment of a method for remote version management of a work provided herein;
FIG. 2 is a schematic structural diagram of an embodiment of an electronic device provided in the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a computer storage medium provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.
The remote version management method for the works is applied to an electronic device, specifically can be a user side, and the user side can be an electronic device such as a smart phone, a computer, a tablet personal computer and an intelligent wearable device.
Referring to fig. 1, fig. 1 is a schematic flowchart of an embodiment of a remote version management method for a work provided by the present application, which specifically includes the following steps:
s101: dividing local version data of the work into a plurality of data files, and sequentially sending the data files to a Git server, wherein the data files comprise version record files.
The animation programming software is installed on the user side, the user uses the animation programming software to create works through the user side, and in the creation process or after creation is finished, the user can locally store the current works through the user side and upload the works to the Git server to remotely store the works, and the works are shared by other users.
Specifically, a user can generate a remote version saving instruction of the work by clicking an upload sharing button in animation programming software, and when the user side receives the remote version saving instruction of the work, the user side extracts the current local version data of the work, divides the current local version data into a plurality of independent data files, and then sequentially sends the plurality of data files to the Git server. The user side of the embodiment divides the current local version data into a plurality of independent data files, which is beneficial to reducing the real-time transmission amount in the transmission process and improving the fault tolerance rate in the transmission process. The local version data of the works are version composition data of the works recorded under the local server, and a user can directly load the local version data from the local server through animation programming software, so that the editing state of the works under the version is displayed in the animation programming software.
The plurality of data files comprise version record files, and the version record files are all used as the last data file to be sent to the Git server in the process of transmitting the complete local version data each time.
In the Git server (distributed version control Git server) of the present embodiment, Git (distributed version control system) is mounted on a server or a server cluster. Git, as an open source distributed version control system, can efficiently handle project version management from very small to very large.
In some embodiments, the step of sending the plurality of data files to the Git server in sequence comprises: obtaining previous remote version data of the work; comparing the previous remote version data with the current local version data to obtain a target data file, wherein the target data file is a data file which is different from the previous remote version data in the current local version data; and sequentially sending the target data files to the Git server.
Specifically, in order to reduce the data transmission amount, not repeatedly send the same data files, and improve the data transmission efficiency, in the process of dividing the local version data of the work into a plurality of data files, and sequentially sending the plurality of data files to the Git server, the previous remote version data of the work is firstly obtained, the previous remote version data is compared with the current local version data of the work, a data file different from the previous remote version data in the current local version data is obtained as a target data file, and only the target data files are sent to the Git server, the data files identical to the previous remote version data in other current local version data are not repeatedly sent, the different data files related by the embodiment include data files with changed data information and data files with newly increased and decreased data of the current local version data relative to the previous remote version data, the previous remote version is the remote version that the user last uploaded to the Git server.
In a specific embodiment, the step of obtaining previous remote version data of the work, and comparing the previous remote version data with current local version data to obtain a target data file includes: obtaining a hash value corresponding to a previous remote version data file of the work; performing hash calculation on the current local version data file to obtain a hash value corresponding to the current local version data file; and comparing the hash value corresponding to the previous remote version data file with the hash value corresponding to the current local version data file one by one to obtain a data file which is different from the previous remote version data in the current local version data and is used as a target data file.
Because the hash value and the corresponding data files are in one-to-one correspondence, and the corresponding hash value is unique for the data files with the same data information. When any change occurs in the data information of the data file, the corresponding generated hash value also changes. Therefore, whether the data file changes or not can be monitored by mapping the corresponding data file through the hash value. Specifically, in the process of comparing the hash value corresponding to the data file of the previous remote version with the hash value corresponding to the data file of the current local version one by one, for the data file of which both versions exist and the name is the same, if the hash values corresponding to the two versions are different, it indicates that the data information of the data file in the current local version is changed and needs to be sent to the Git server for updating, and if the hash values corresponding to the two versions are the same, it indicates that the data information of the data file in the current local version is not changed, and the data file does not need to be sent to the Git server again; for newly added data files in the current local version data relative to the previous remote version data, the newly added data files need to be sent to a Git server to be added as data files of the current remote version; and for the data files with the data reduced relative to the previous remote version data in the current local version data, the data files in the current local version data are deleted, and only the deleted information of the data files needs to be sent to the Git server, so that correspondingly, when the current remote version data is generated, the data files in the current remote version data are also deleted.
In some embodiments, the step of sequentially sending the plurality of data files of the work to the Git server further comprises: when any one of the data files fails to be transmitted during the process of sequentially transmitting the plurality of data files to the Git server, the transmission process is interrupted, and when the data files are transmitted again, the plurality of data files which are not transmitted yet are sequentially transmitted from the data file which fails to be transmitted currently.
Specifically, in order to reduce the data transmission amount, not repeatedly send the same data files and improve the data transmission efficiency, in the process of dividing the local version data of the work into a plurality of data files and sequentially sending the data files to the Git server, when any one of the data files fails to be sent, the sending process of the whole version data is interrupted, the data file which fails to be sent currently can be used as a breakpoint, when the version data is sent again, the data file which fails to be sent currently is used as a first data file from the breakpoint and a plurality of data files which are not sent yet are sequentially sent, and the data file which is sent successfully before the breakpoint is not repeatedly sent any more.
In a specific embodiment, in the process of sequentially sending the plurality of data files of the work to the Git server, the method further includes: and generating prompt information according to the progress of sending the plurality of data files. Specifically, the prompt information includes the name and progress of the currently transmitted data file, the transmission status, and the like. Through the prompt information, the user can acquire the state of the data file in the transmission process in real time.
S102: and receiving file identification numbers corresponding to the plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files.
After receiving the plurality of data files sent by the user side, the Git server generates a corresponding unique file identification number according to each data file, stores the plurality of data files according to the file identification numbers, and returns the file identification numbers to the user side.
In some embodiments, the step of the Git server generating a corresponding unique file identification number from each data file comprises: the Git server calculates each data file by adopting a hash algorithm to generate a hash value corresponding to each data file, and generates a file identification number corresponding to each data file according to each hash value.
Specifically, the Git server receives a plurality of data files sequentially sent by the user side, and calculates each data file through a hash algorithm to obtain a corresponding hash value. And generating file identification numbers corresponding to the files according to the hash values, wherein the file identification numbers can be in a digital ID form. At this time, the data file is stored in one storage space or distributed in a plurality of storage spaces, and the file identification number records the storage address of the corresponding data file, so that the Git server or the client can quickly locate the corresponding data file through the file identification number.
S103: and when the version record file identification number corresponding to the version record file is received, generating remote version information according to the version record file identification number.
And when the client receives the version record file identification number corresponding to the version record file, all the data files of the local version data are uploaded to the Git server. The user side generates remote version information according to the received version record file identification number, the remote version information comprises a remote version number and remote version address information, and other users can load remote version data of the work through the remote version address information. The user can switch between the local version and the remote version at will and synchronize at any time.
In a specific embodiment, the step of generating the remote version information according to the version record file identification number includes: and acquiring file identification numbers of a plurality of data files corresponding to the current local version data according to the version record file identification numbers, and generating current remote version information according to the file identification numbers.
Specifically, when a version record file identification number corresponding to a version record file is received, it can be determined that all data files of the current local version data are uploaded according to the version record file identification number, at this time, file identification numbers of a plurality of data files corresponding to the current local version data are obtained, the plurality of data files corresponding to the current local version data and the version record file are used as remote version data, and current remote version information is generated according to the plurality of file identification numbers.
In the embodiment of the application, the local version data of the work is divided into a plurality of data files which are sequentially sent to a Git server, and the plurality of data files comprise version record files; receiving file identification numbers corresponding to the plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files; and when the version record file identification number corresponding to the version record file is received, generating remote version information according to the version record file identification number. According to the remote version management method for the works, the local version data are divided into the plurality of independent data files, the plurality of independent data files are sequentially sent to the Git server, the remote version information is generated, a remote version management function is provided for animation programming software, the works can be conveniently shared by a user, and the fault tolerance rate of data sending can be effectively improved.
In order to implement the remote version management method for the works, the present application further provides an electronic device, and specifically refer to fig. 2, where fig. 2 is a schematic structural diagram of an embodiment of the electronic device provided in the present application.
As shown in fig. 2, the electronic device 200 of the present embodiment includes a processor 21, a memory 22, an input-output device 23, and a bus 24.
The processor 21, the memory 22 and the input/output device 23 are respectively connected to the bus 24, the memory 22 stores program data, and the processor 21 is configured to execute the program data to implement the remote version management method for the work according to the above embodiment.
In the present embodiment, the processor 21 may also be referred to as a CPU (Central Processing Unit). The processor 21 may be an integrated circuit chip having signal processing capabilities. The processor 21 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor 21 may be any conventional processor or the like.
The present application also provides a computer storage medium, as shown in fig. 3, a computer storage medium 300 for storing program data 31, the program data 31, when executed by a processor, is used to implement the method as described in the embodiments of the remote version management method for a work provided in the present application.
The method involved in the embodiment of the work remote version management method provided by the application exists in the form of a software functional unit when being implemented and is sold or used as an independent product, and can be stored in a device, such as a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for remote version management of a work, the method comprising:
dividing local version data of a work into a plurality of data files, and sequentially sending the data files to a Git server, wherein the data files comprise version record files;
receiving file identification numbers corresponding to a plurality of data files, wherein the file identification numbers are generated by the Git server according to the plurality of data files;
and when receiving the version record file identification number corresponding to the version record file, generating remote version information according to the version record file identification number.
2. The remote work version management method of claim 1, wherein the step of sequentially transmitting the plurality of data files to a Git server further comprises:
and the version record file is used as the last data file and sent to the Git server.
3. The remote work version management method of claim 1, wherein the Git server computes each data file using a hash algorithm to generate a hash value corresponding to each data file, and generates a file identification number corresponding to each data file from each hash value.
4. The remote work version management method of claim 1, wherein the step of sequentially transmitting the plurality of data files to the Git server comprises:
obtaining previous remote version data of the work, and comparing the previous remote version data with current local version data to obtain a target data file, wherein the target data file is a data file which is different from the previous remote version data in the current local version data;
and sequentially sending the target data files to the Git server.
5. The remote work version management method of claim 4, wherein the step of obtaining previous remote version data of the work, comparing the previous remote version data with current local version data to obtain a target data file comprises:
obtaining a hash value corresponding to a previous remote version data file of the work;
performing hash calculation on the current local version data file to obtain a hash value corresponding to the current local version data file;
and comparing the hash value corresponding to the previous remote version data file with the hash value corresponding to the current local version data file one by one to obtain a data file different from the previous remote version data in the current local version data as a target data file.
6. The remote work version management method of claim 1, wherein the step of sequentially transmitting the plurality of data files to a Git server further comprises:
when any one of the data files fails to be transmitted in the process of sequentially transmitting the data files to the Git server, the transmission process is interrupted, and when the data files are transmitted again, the plurality of data files which are not transmitted yet are sequentially transmitted from the data file which fails to be transmitted currently.
7. The remote work version management method of claim 1, wherein the step of sequentially transmitting the plurality of data files to a Git server further comprises:
and generating prompt information according to the progress sent by the plurality of data files.
8. The remote work version management method according to claim 1, wherein said step of generating remote version information based on said version record file identification number comprises:
and acquiring file identification numbers of a plurality of data files corresponding to the current local version data according to the version record file identification numbers, and generating current remote version information according to the file identification numbers.
9. An electronic device comprising a memory, a processor, and program data stored on the memory and executable on the processor, the processor implementing the steps of the method of remote version management of a work according to any one of claims 1 to 8 when executing the program data.
10. A computer storage medium for storing program data which, when executed by a processor, is adapted to carry out the steps of a method of remote version management of a work according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010924217.7A CN112148350A (en) | 2020-09-04 | 2020-09-04 | Remote version management method for works, electronic device and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010924217.7A CN112148350A (en) | 2020-09-04 | 2020-09-04 | Remote version management method for works, electronic device and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112148350A true CN112148350A (en) | 2020-12-29 |
Family
ID=73890984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010924217.7A Pending CN112148350A (en) | 2020-09-04 | 2020-09-04 | Remote version management method for works, electronic device and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148350A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687846A (en) * | 2021-06-30 | 2021-11-23 | 北京百度网讯科技有限公司 | Method, apparatus, device and readable storage medium for processing data |
| CN113986827A (en) * | 2021-10-21 | 2022-01-28 | 富士胶片（中国）投资有限公司 | File multi-version management method and corresponding server |
| CN115238257A (en) * | 2022-09-26 | 2022-10-25 | 深圳市亲邻科技有限公司 | Access control face permission updating method and device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009110061A (en) * | 2007-10-26 | 2009-05-21 | Nec Corp | Version management system and version management method |
| CN103095843A (en) * | 2013-01-28 | 2013-05-08 | 刘海峰 | Method and client of data backup based on version vectors |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN109558382A (en) * | 2018-12-06 | 2019-04-02 | Oppo广东移动通信有限公司 | File management method, electronic device and computer readable storage medium |
| CN110196840A (en) * | 2019-05-22 | 2019-09-03 | 中至数据集团股份有限公司 | Document management method, device, readable storage medium storing program for executing and computer equipment |
-
2020
- 2020-09-04 CN CN202010924217.7A patent/CN112148350A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009110061A (en) * | 2007-10-26 | 2009-05-21 | Nec Corp | Version management system and version management method |
| CN103095843A (en) * | 2013-01-28 | 2013-05-08 | 刘海峰 | Method and client of data backup based on version vectors |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN109558382A (en) * | 2018-12-06 | 2019-04-02 | Oppo广东移动通信有限公司 | File management method, electronic device and computer readable storage medium |
| CN110196840A (en) * | 2019-05-22 | 2019-09-03 | 中至数据集团股份有限公司 | Document management method, device, readable storage medium storing program for executing and computer equipment |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687846A (en) * | 2021-06-30 | 2021-11-23 | 北京百度网讯科技有限公司 | Method, apparatus, device and readable storage medium for processing data |
| CN113687846B (en) * | 2021-06-30 | 2023-07-18 | 北京百度网讯科技有限公司 | Method, apparatus, device and readable storage medium for processing data |
| CN113986827A (en) * | 2021-10-21 | 2022-01-28 | 富士胶片（中国）投资有限公司 | File multi-version management method and corresponding server |
| CN115238257A (en) * | 2022-09-26 | 2022-10-25 | 深圳市亲邻科技有限公司 | Access control face permission updating method and device, computer equipment and storage medium |
| CN115238257B (en) * | 2022-09-26 | 2023-01-06 | 深圳市亲邻科技有限公司 | Access control face permission updating method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112148350A (en) | Remote version management method for works, electronic device and computer storage medium | |
| US10891305B2 (en) | Synchronization of data between systems | |
| CN110689349B (en) | Transaction hash value storage and searching method and device in blockchain | |
| JP2019518257A (en) | State control method and apparatus | |
| US10467192B2 (en) | Method and apparatus for updating data table in keyvalue database | |
| CN109919691B (en) | Data processing system, method and device | |
| EP4300323A1 (en) | Data processing method and apparatus for blockchain network, computer device, computer readable storage medium, and computer program product | |
| CN108108285A (en) | Log processing method, device, storage medium and terminal device | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| WO2020216077A1 (en) | Blockchain event deduplication method and apparatus, and computer device and storage medium | |
| WO2024001024A1 (en) | Method for executing transaction in blockchain system, and blockchain system and nodes | |
| CN112486915A (en) | Data storage method and device | |
| CN113051102B (en) | File backup method, device, system, storage medium and computer equipment | |
| WO2017084020A1 (en) | Method and apparatus for model parameter fusion | |
| CN114679457A (en) | Node grouping method in block chain and block chain link point | |
| US10394773B2 (en) | Determining when a change set was delivered to a workspace or stream and by whom | |
| CN109729121B (en) | Cloud storage system and method for realizing custom data processing in cloud storage system | |
| CN116800671A (en) | Data transmission method, apparatus, computer device, storage medium, and program product | |
| CN106790445A (en) | Data transmission method, device and electronic equipment based on Samba agreements | |
| CN116108042A (en) | Data processing method, device, electronic equipment, storage medium and program product | |
| CN114245173B (en) | Image compression method, device, terminal equipment and storage medium | |
| CN115695326A (en) | Data frame transmission method and device, computer equipment and storage medium | |
| CN114513469A (en) | Traffic shaping method and device for distributed system and storage medium | |
| CN116208676A (en) | Data back-source method, device, computer equipment, storage medium and program product | |
| CN114116256A (en) | Variable calling method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |