CN105975567B - Method and device for processing internal file of application program - Google Patents
Method and device for processing internal file of application program Download PDFInfo
- Publication number
- CN105975567B CN105975567B CN201610286771.0A CN201610286771A CN105975567B CN 105975567 B CN105975567 B CN 105975567B CN 201610286771 A CN201610286771 A CN 201610286771A CN 105975567 B CN105975567 B CN 105975567B
- Authority
- CN
- China
- Prior art keywords
- file
- internal
- read
- internal file
- address
- 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
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000013507 mapping Methods 0.000 claims abstract description 89
- 230000001960 triggered effect Effects 0.000 claims abstract description 11
- 238000010586 diagram Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000003672 processing method Methods 0.000 description 4
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- 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/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
- G06F16/166—File name conversion
-
- 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/13—File access structures, e.g. distributed indices
-
- 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/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a mobile intelligent terminal, in particular to a method and a device for processing an internal file of an application program, wherein the method comprises the steps of judging whether an address mapping relation corresponding to the internal file is recorded or not when the processing flow of the internal file of the application program is triggered; the address mapping relation represents an internal address path of the internal file in the application program and a corresponding relation between the internal address path and the preset address path of the internal file; presetting an address path, which represents a public address path that all application programs can access; when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path; when the read file is determined to be the same as the internal file, the read file is correspondingly processed, so that the internal file does not need to be stored once during each processing, the internal file processing speed is increased, redundant files are reduced, and the resource utilization rate is improved.
Description
Technical Field
The present invention relates to a mobile intelligent terminal, and in particular, to a method and an apparatus for processing an internal file of an application program.
Background
At present, internal files of Android applications are generally stored in, for example, a/data/data/com/directory, the directory is a private directory of the application, and access permissions of other applications are limited, so that other applications are opened or shared to other applications by directly using the path, sometimes the path cannot be opened, some applications have reading permissions, but no editing permissions exist, and some functions are not available. For example, when a picture in the multimedia message is opened by using a google album, the picture cannot be edited, and thus, the clipping function cannot be realized. For another example, pictures in the information are shared to the WeChat, and the WeChat does not necessarily have the authority to read the pictures in the information, so that the sharing cannot be completed; also, due to the permission limitation of the internal file of the application program, the pictures in the information may not be opened and edited by some third-party software.
In the prior art, common solutions for processing an internal file of an Android application program include the following two types:
the first method comprises the following steps: the internal file of the application program only provides a storage function, and enters the file manager for operation after being stored in the terminal U disk or the SD card. The second method comprises the following steps: and when the internal file is shared each time, the internal file is stored locally, and then the stored file path is shared.
Therefore, in the prior art, the processing method of the internal file has complex operation steps, and the internal file needs to be stored locally and then sent to the file manager for processing each time; moreover, the internal file is saved once every time processing is performed, resulting in a large number of duplicate files.
Disclosure of Invention
The embodiment of the invention provides a method and a device for processing an internal file of an application program, which aim to solve the problem that the processing operation efficiency of the internal file of the application program is not high in the prior art.
The embodiment of the invention provides the following specific technical scheme:
a processing method of internal files of an application program comprises the following steps:
running an application program, and judging whether an address mapping relation corresponding to an internal file of the application program is recorded or not when the processing flow of the internal file is triggered; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs;
when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path;
and when the read file is determined to be the same as the internal file, performing corresponding processing on the read file.
An apparatus for processing an internal file of an application, comprising:
the judging unit is used for running an application program and judging whether an address mapping relation corresponding to an internal file is recorded or not when the processing flow of the internal file of the application program is determined to be triggered; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs;
a reading unit, configured to determine a corresponding preset address path based on the internal address path and the address mapping relationship when the address mapping relationship is recorded, and read a corresponding file from the preset address path;
and the processing unit is used for performing corresponding processing on the read file when the read file is determined to be the same as the internal file.
The invention has the following beneficial effects:
in the embodiment of the invention, when an application program is operated and the processing flow of an internal file of the application program is determined to be triggered, whether an address mapping relation corresponding to the internal file is recorded is judged; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs; when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path; when the read file is determined to be the same as the internal file, the read file is correspondingly processed, so that a preset address path corresponding to the internal file is determined from the recorded address mapping relation, and the corresponding file is read from the preset address path, the internal file does not need to be stored once each time, the operation is simple, the internal file processing speed is increased, redundant files are reduced, and the resource utilization rate is improved; when the file is read, a judgment process is added, and the accuracy of internal file processing is improved.
Drawings
FIG. 1 is a flowchart illustrating an overview of a method for processing internal files of an application according to an embodiment of the present invention;
FIG. 2 is a detailed flowchart of a processing method for internal files of an application according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a device for processing an internal file of an application according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
In order to solve the problem of low processing operation efficiency of internal files of application programs in the prior art, in the embodiment of the invention, when the processing flow of the internal files of the application programs is determined to be triggered, whether the address mapping relation corresponding to the internal files is recorded or not is judged, when the recording is determined, the corresponding files are read from the preset address path, and when the read files are determined to be the same as the internal files, the read files are correspondingly processed.
The present invention will be described in detail with reference to specific examples, but it is to be understood that the present invention is not limited to the examples.
Referring to fig. 1, in the embodiment of the present invention, a specific flow of a method for processing an internal file of an application program is as follows:
step 100: running an application program, and judging whether an address mapping relation corresponding to an internal file of the application program is recorded or not when the processing flow of the internal file is triggered; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs.
In practice, the internal file of the application program is stored in the private directory of the application program, and the private directory has access right to other application programs, and if other application programs need to open the internal file or share the internal file with other application programs, the internal file needs to be stored in a public address path, and then corresponding processing is performed.
In the embodiment of the present invention, an address mapping relationship corresponding to an internal file may be recorded, and specifically, a field, for example, a share path (share _ path) field, may be added in the database to mark an address mapping relationship corresponding to a current internal file, that is, a corresponding relationship between an internal address path of the internal file in an application program and a preset address path of the internal file.
The preset address path may be in a phone U disk or an SD card of the terminal, or may be other public address paths, which is not limited.
Therefore, when the processing flow of the internal file is determined to be triggered, the preset address path is determined directly from the address mapping relation of the internal file recorded in the database, the searching speed of the preset address path is accelerated, and an address path does not need to be generated every time.
Step 110: and when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path.
When step 110 is executed, the method specifically includes:
first, when the address mapping relationship is determined to be recorded, a corresponding preset address path is determined based on the internal address path and the address mapping relationship.
For example, for an internal file of an application program, the internal address path of the internal file in the application program is: and the internal file is stored in a preset address path as follows: andcard represents that the current storage location is an SD card, and com. When the address mapping relation is determined to be recorded, it can be determined that the internal file is stored in the public address path, i.e. the preset address path/SD/com.
And then, reading the corresponding file from the preset address path.
Further, when it is determined that the address mapping relationship is not recorded, the corresponding file is directly read from the default address path.
This is because, when processing an internal file, the internal file needs to be saved in a public address path, and this public address path may be set in advance, and the internal file is generally saved in the public address path, and when an address mapping relationship corresponding to the internal file is not recorded, there is a high possibility that the internal file is already saved in the public address path, where a default address path and a preset address path may be the same or different, and both are one of the public address paths and are preset.
Therefore, when no record is determined, the corresponding file can be directly read from the default address path, and the processing speed is increased.
Step 120: and when the read file is determined to be the same as the internal file, performing corresponding processing on the read file.
That is, when reading a file, it is determined once whether the read file is the same as the internal file, because when reading, the file is read from a predetermined address path corresponding to the internal file, where the predetermined address path includes a name of the file, but there may be a case where the file names are the same but different.
For example, the preset address path corresponding to the internal file is: the method includes the steps of reading an a.jpg file, and performing a corresponding processing on the read a.jpg file directly.
When the step 120 is executed, the method specifically includes:
first, it is judged whether the read file is the same size as the above internal file, and when the read file is determined to be the same size, it is further judged whether the read file is the same message digest algorithm (MD5) value as the above internal file, and when the read file is determined to be the same MD5 value, it is determined that the read file is the same as the above internal file.
The MD5 is an encryption algorithm that can uniquely identify a file, and is also called a hash algorithm, and of course, other algorithms may also be used to determine whether the files are the same, and the embodiment of the present invention is not limited.
It should be noted that, the reason why the sizes of the files are the same is that the judgment of the sizes of the files is relatively simple, and when the sizes of the files are determined to be different, the sizes of the read files and the internal files can be directly determined to be different, so that the speed and the time for comparing the files are accelerated; when the file sizes are the same, whether the MD5 are the same or not is judged, and the accuracy of file comparison is improved on the premise of ensuring the file comparison speed.
Then, the read file is processed correspondingly.
For example, the read file is shared with other application programs, or the read file is opened using other application programs.
Further, when it is determined that the address mapping relationship is not recorded, the corresponding file is directly read from the default address path, and when it is determined that the read file is the same as the internal file, the address mapping relationship corresponding to the internal file is recorded according to the default address path and the internal address path of the internal file, and the read file is correspondingly processed.
Further, when it is determined that a corresponding file is not read, or that the read file is different from the internal file, the following two cases may be specifically classified:
in the first case: and when the address mapping relation is determined not to be recorded, renaming the internal file according to a preset naming rule, storing the renamed internal file under the default address path, and recording the address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file.
That is to say, the internal file is not stored in the default address path, so that the corresponding file cannot be read from the default address path, or it is determined that the read file is different from the internal file, at this time, the internal file needs to be stored in the default address path again, and the address mapping relationship corresponding to the internal file is recorded, so that when the internal file is processed next time, the internal file does not need to be stored in the default address path again, which saves processing time, and does not need to be stored every time, reduces redundant files of the system, and improves resource utilization rate.
In the second case: deleting the address mapping relation corresponding to the internal file when the address mapping relation is determined to be recorded; renaming the internal file according to a preset naming rule, storing the renamed internal file into the preset address path, and recording the address mapping relation corresponding to the internal file again.
That is, although there is a record, the corresponding preset address path is determined, but the corresponding file under the preset address path may have been deleted or the path does not exist, so that the corresponding file cannot be read, or it is determined that the read file is different from the internal file, at this time, it is necessary to save the internal file in the preset address path again and record the address mapping relationship corresponding to the internal file.
When the read file is determined to be different from the internal file, and the internal file is renamed, the renamed file name needs to be different from the read file name, so that the corresponding file can be read correctly when the file is read again next time.
The above embodiments are further described in detail below using a specific application scenario. Specifically, referring to fig. 2, in the embodiment of the present invention, an execution process of the processing method for the internal file of the application program is specifically as follows:
step 200: and triggering the processing flow of the internal file of the application program.
For example, clicking to share the internal file to other applications or to open the internal file using other applications.
Step 201: and judging whether the address mapping relation corresponding to the internal file is recorded, if so, executing step 202, otherwise, executing step 207.
Specifically, the recorded address mapping relationship corresponding to the internal file is stored in a preset database, so that whether the address mapping relationship corresponding to the internal file is recorded or not can be directly searched from the database.
The address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file.
Step 202: and judging whether a corresponding file is read, if so, executing the step 203, otherwise, executing the step 206.
Specifically, a preset address path of the internal file is determined according to the address mapping relationship, and since a corresponding file may be deleted or the preset address path does not exist, it is determined whether the corresponding file can be read from the preset address path.
Step 203: and judging whether the size of the read file is the same as that of the internal file, if so, executing step 204, otherwise, executing step 206.
Therefore, judgment is carried out according to the file size, the judgment is simple, and if the judgment is different, the result can be quickly compared.
Step 204: and judging whether the read file and the internal file MD5 have the same value, if so, executing the step 205, otherwise, executing the step 206.
Therefore, whether the sizes of the files are the same or not is judged firstly, and when the sizes are the same, the judgment is carried out through the MD5 value, so that the accuracy of file comparison is improved on the premise of ensuring the comparison speed.
Step 205: and correspondingly processing the read file.
Step 206: the address mapping relationship corresponding to the internal file is deleted and the process goes to step 212.
Step 207: the corresponding file is read directly from the default address path.
The default address path and the preset address path may be the same or different, and may be preset in advance.
In this way, for the situation that no record exists but the record is stored in the default address path, the searching speed is faster than the speed of newly generating the address path for the internal file and storing the address path, the internal file processing speed can be increased, and the time can be saved.
Step 208: and judging whether the corresponding file is read, if so, executing the step 209, otherwise, executing the step 212.
Step 209: it is determined whether the size of the read file is the same as the size of the internal file, if so, step 210 is performed, otherwise, step 212 is performed.
Step 210: and judging whether the read file and the internal file MD5 have the same value, if so, executing step 211, otherwise, executing step 212.
Step 211: and correspondingly processing the read file.
Step 212: and renaming the internal file, and saving the renamed internal file to a corresponding address path.
For example, in the case where it is determined that the address mapping relation corresponding to the internal file is not recorded, the renamed internal file is saved in the default address path.
For another example, when the address mapping relationship corresponding to the internal file is determined to be recorded, the renamed internal file is saved to the preset address path.
Step 213: the address mapping relationship corresponding to the internal file is recorded again, and the process goes to step 211.
Based on the foregoing embodiment, referring to fig. 3, in an embodiment of the present invention, a processing apparatus for an internal file of an application program specifically includes:
a determining unit 30, configured to run an application program, and determine whether an address mapping relationship corresponding to an internal file of the application program is recorded when a processing flow of the internal file is triggered; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs;
a reading unit 31, configured to determine a corresponding preset address path based on the internal address path and the address mapping relationship when the address mapping relationship is recorded, and read a corresponding file from the preset address path;
and a processing unit 32, configured to perform corresponding processing on the read file when it is determined that the read file is the same as the internal file.
Preferably, when determining whether the address mapping relationship corresponding to the internal file is recorded, the reading unit 31 is further configured to:
when the address mapping relation is determined not to be recorded, directly reading a corresponding file from a default address path;
the processing unit 32 is further configured to: and when the read file is determined to be the same as the internal file, recording an address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file, and performing corresponding processing on the read file.
Preferably, when it is determined that the read file is the same as the internal file, the processing unit 32 is specifically configured to:
judging whether the size of the read file is the same as that of the internal file, when the size is the same, further judging whether the MD5 value of the read file is the same as that of the internal file, and when the MD5 value is the same, determining that the read file is the same as that of the internal file.
Preferably, when it is determined that the address mapping relationship is not recorded, the method further includes:
the first recording unit 33 is configured to rename the internal file according to a preset naming rule when it is determined that the corresponding file is not read or the read file is different from the internal file, store the renamed internal file in the default address path, and record an address mapping relationship corresponding to the internal file according to the default address path and the internal address path of the internal file.
Preferably, when determining that the address mapping relationship is recorded, the method further includes the second recording unit 34:
when it is determined that the corresponding file is not read or the read file is different from the internal file, deleting the address mapping relation corresponding to the internal file;
renaming the internal file according to a preset naming rule, storing the renamed internal file into the preset address path, and recording the address mapping relation corresponding to the internal file again.
In summary, in the embodiment of the present invention, when an application program is run and a processing flow of an internal file of the application program is determined to be triggered, whether an address mapping relationship corresponding to the internal file is recorded is determined; the address mapping relation represents the corresponding relation between the internal address path of the internal file in the application program and the preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs; when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path; when the read file is determined to be the same as the internal file, the read file is correspondingly processed, so that a preset address path corresponding to the internal file is determined from the recorded address mapping relation, the corresponding file is read from the preset address path, the internal file is not required to be stored in the preset address path every time, a temporary directory is not required to be generated every time, the internal file processing speed is increased, redundant files are reduced, and the resource utilization rate is improved; when the file is read, a judgment process is added, and the accuracy of internal file processing is improved.
And, whether the read file is the same as the internal file is judged through the size of the file and the MD5, so that the speed of file comparison is improved, and the accuracy of file comparison is improved.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (10)
1. A method for processing internal files of an application program is characterized by comprising the following steps:
the method comprises the steps of running an application program, and judging whether an address mapping relation corresponding to an internal file is recorded or not when the processing flow of the internal file of the application program is determined to be triggered; the address mapping relation represents an internal address path of the internal file in the application program and a corresponding relation between the internal address path and a preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs;
when the address mapping relation is determined to be recorded, determining a corresponding preset address path based on the internal address path and the address mapping relation, and reading a corresponding file from the preset address path;
and when the read file is determined to be the same as the internal file, performing corresponding processing on the read file.
2. The method of claim 1, wherein when determining whether the address mapping relationship corresponding to the internal file is recorded, the method further comprises:
when the address mapping relation is determined not to be recorded, directly reading a corresponding file from a default address path;
and when the read file is determined to be the same as the internal file, recording an address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file, and performing corresponding processing on the read file.
3. The method according to claim 1 or 2, wherein determining that the read file is the same as the internal file specifically comprises:
and judging whether the read file and the internal file have the same size, further judging whether the read file and the internal file have the same message digest algorithm MD5 value when the read file and the internal file have the same size, and determining that the read file and the internal file have the same value when the read file and the internal file have the same MD5 value.
4. The method of claim 2, wherein when it is determined that the address mapping relationship is not recorded, further comprising:
when it is determined that no corresponding file is read or the read file is different from the internal file, renaming the internal file according to a preset naming rule, storing the renamed internal file in the default address path, and recording an address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file.
5. The method of claim 1 or 2, wherein when determining that the address mapping relationship is recorded, further comprising:
when it is determined that the corresponding file is not read or the read file is different from the internal file, deleting the address mapping relation corresponding to the internal file;
renaming the internal file according to a preset naming rule, storing the renamed internal file under the preset address path, and recording the address mapping relation corresponding to the internal file again.
6. An apparatus for processing internal files of an application, comprising:
the judging unit is used for running an application program and judging whether an address mapping relation corresponding to an internal file is recorded or not when the processing flow of the internal file of the application program is determined to be triggered; the address mapping relation represents an internal address path of the internal file in the application program and a corresponding relation between the internal address path and a preset address path of the internal file; the preset address path represents a public address path which can be accessed by all application programs;
a reading unit, configured to determine, when the address mapping relationship is recorded, a corresponding preset address path based on the internal address path and the address mapping relationship, and read a corresponding file from the preset address path;
and the processing unit is used for performing corresponding processing on the read file when the read file is determined to be the same as the internal file.
7. The apparatus of claim 6, wherein when determining whether an address mapping relationship corresponding to the internal file is recorded, the reading unit is further configured to:
when the address mapping relation is determined not to be recorded, directly reading a corresponding file from a default address path;
the processing unit is further to: and when the read file is determined to be the same as the internal file, recording an address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file, and performing corresponding processing on the read file.
8. The apparatus according to claim 6 or 7, wherein the processing unit is specifically configured to, upon determining that the read file is identical to the internal file:
and judging whether the read file and the internal file have the same size, further judging whether the read file and the internal file have the same message digest algorithm MD5 value when the read file and the internal file have the same size, and determining that the read file and the internal file have the same value when the read file and the internal file have the same MD5 value.
9. The apparatus of claim 7, wherein when it is determined that the address mapping relationship is not recorded, further comprising:
the first recording unit is used for renaming the internal file according to a preset naming rule when the corresponding file is determined not to be read or the read file is different from the internal file, storing the renamed internal file into the default address path, and recording the address mapping relation corresponding to the internal file according to the default address path and the internal address path of the internal file.
10. The apparatus according to claim 6 or 7, wherein when determining that the address mapping relationship is recorded, further comprising the second recording unit configured to:
when it is determined that the corresponding file is not read or the read file is different from the internal file, deleting the address mapping relation corresponding to the internal file;
renaming the internal file according to a preset naming rule, storing the renamed internal file under the preset address path, and recording the address mapping relation corresponding to the internal file again.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610286771.0A CN105975567B (en) | 2016-05-03 | 2016-05-03 | Method and device for processing internal file of application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610286771.0A CN105975567B (en) | 2016-05-03 | 2016-05-03 | Method and device for processing internal file of application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105975567A CN105975567A (en) | 2016-09-28 |
| CN105975567B true CN105975567B (en) | 2019-12-20 |
Family
ID=56994478
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610286771.0A Active CN105975567B (en) | 2016-05-03 | 2016-05-03 | Method and device for processing internal file of application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105975567B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528690B (en) * | 2016-10-31 | 2019-08-20 | 维沃移动通信有限公司 | A kind of method and mobile terminal of application program accessing storage media |
| CN109684278A (en) * | 2018-12-21 | 2019-04-26 | 广州酷狗计算机科技有限公司 | File acquisition method, device, terminal and storage medium |
| CN112464225A (en) * | 2020-10-30 | 2021-03-09 | 数网金融有限公司 | Request processing method, request processing device and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102906754A (en) * | 2010-05-20 | 2013-01-30 | 桑迪士克以色列有限公司 | Host device and method for accessing a virtual file in a storage device by bypassing a cache in the host device |
| CN103383660A (en) * | 2013-04-01 | 2013-11-06 | 华为终端有限公司 | Method and device for realizing functions of cache partition of Android system as well as terminal equipment |
| CN104951482A (en) * | 2014-03-31 | 2015-09-30 | 炬芯（珠海）科技有限公司 | Method and device for operating Sparse-format mirror image document |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101334823B (en) * | 2008-07-17 | 2010-07-07 | 成都市华为赛门铁克科技有限公司 | File virtualization processing method and device |
-
2016
- 2016-05-03 CN CN201610286771.0A patent/CN105975567B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102906754A (en) * | 2010-05-20 | 2013-01-30 | 桑迪士克以色列有限公司 | Host device and method for accessing a virtual file in a storage device by bypassing a cache in the host device |
| CN103383660A (en) * | 2013-04-01 | 2013-11-06 | 华为终端有限公司 | Method and device for realizing functions of cache partition of Android system as well as terminal equipment |
| CN104951482A (en) * | 2014-03-31 | 2015-09-30 | 炬芯（珠海）科技有限公司 | Method and device for operating Sparse-format mirror image document |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105975567A (en) | 2016-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2863310B1 (en) | Data processing method and apparatus, and shared storage device | |
| KR20170123336A (en) | File manipulation method and apparatus | |
| CN106933823B (en) | Data synchronization method and device | |
| US9298561B1 (en) | Systems and methods for prioritizing restoration speed with deduplicated backups | |
| CN107870802B (en) | Virtual machine migration method and device | |
| CN105975567B (en) | Method and device for processing internal file of application program | |
| CN108874379B (en) | Page processing method and device | |
| WO2016029441A1 (en) | File scanning method and apparatus | |
| CN104346194A (en) | Method, device and electronic equipment for starting file loading | |
| CN106682021A (en) | Database migration method and device | |
| CN112579623A (en) | Method, device, storage medium and equipment for storing data | |
| WO2021169163A1 (en) | File data access method and apparatus, and computer-readable storage medium | |
| CN110647463B (en) | Method and device for restoring test breakpoint and electronic equipment | |
| CN109542860B (en) | Service data management method based on HDFS and terminal equipment | |
| CN106528876B (en) | The information processing method and distributed information processing system of distributed system | |
| EP3108400A1 (en) | Virus signature matching method and apparatus | |
| CN109558249B (en) | Control method and device for concurrent operation | |
| CN112559118A (en) | Application data migration method and device, electronic equipment and storage medium | |
| US20160055168A1 (en) | Method and apparatus for scanning files | |
| CN110019295B (en) | Database retrieval method, device, system and storage medium | |
| CN113515387B (en) | Data processing method and device and electronic device | |
| US20210248117A1 (en) | Database migration method, apparatus, device, and computer-readable medium | |
| US8560572B2 (en) | System for lightweight objects | |
| CN111488557A (en) | Encryption and decryption method and device, electronic equipment and readable storage medium | |
| US10963348B1 (en) | Summary change log indexed by inode numbers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: Shandong City, Qingdao Province, Jiangxi City Road No. 11 Patentee after: Qingdao Hisense Mobile Communication Technology Co.,Ltd. Country or region after: China Address before: Shandong City, Qingdao Province, Jiangxi City Road No. 11 Patentee before: HISENSE MOBILE COMMUNICATIONS TECHNOLOGY Co.,Ltd. Country or region before: China |
|
| CP03 | Change of name, title or address |