CN111338689A - File calling method, device and equipment - Google Patents
File calling method, device and equipment Download PDFInfo
- Publication number
- CN111338689A CN111338689A CN202010147215.1A CN202010147215A CN111338689A CN 111338689 A CN111338689 A CN 111338689A CN 202010147215 A CN202010147215 A CN 202010147215A CN 111338689 A CN111338689 A CN 111338689A
- Authority
- CN
- China
- Prior art keywords
- file
- version
- path information
- node
- search path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000009434 installation Methods 0.000 description 20
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000007670 refining Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002035 prolonged effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 1
- 238000002715 modification method Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 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/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
- G06F9/4486—Formation of subprogram jump address
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Library & Information Science (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a file calling method, a file calling device and a file calling device, wherein the method comprises the steps of receiving a file calling instruction sent by a service system, carrying a file identifier of a file to be called in the file calling instruction, determining a version corresponding to the file to be called according to the file identifier, determining search path information corresponding to the file to be called according to the version, and sequentially searching in a project file according to the node sequence of the search path information until a target file which is the same as the file identifier of the file to be called is obtained, wherein the project file is a plurality of files related to the service system, and the target file is sent to the service system. By adopting the scheme, the calling program is simplified, the calling time of the file is reduced, and the running speed of the service system is further improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a file calling method, a file calling device and file calling equipment.
Background
The secondary development of the software is developed aiming at the personalized requirements of customers on the basis of the existing software products. When the existing product functions cannot meet the requirements of customers or need to be in butt joint with other software to realize data exchange and transmission, secondary development is needed to realize corresponding functions.
In the process of secondary development, the code file may need to be modified to form a new code copy file, and the newly formed code copy file may also need to be modified continuously. For example, in secondary development, modification needs to be made to the code file A, and B, C, D three code copy files are obtained. And modifying the code copy file B to continuously obtain a new code copy file B +.
However, after the software development is completed, the developed software corresponds to a service system, and the service system is used for calling the files obtained in the software development process. When the business system calls the file, it may need to call both replica file B and replica file C. The original file and the modified duplicate file are generally distributed in a scattered manner, the called files are required to be manually placed together each time and then are called by the service system, the calling process is complicated, the calling time of the files is prolonged, and the running speed of the service system is reduced.
Disclosure of Invention
The embodiment of the invention provides a file calling method, a file calling device and file calling equipment, and aims to improve the efficiency of file calling.
In a first aspect, an embodiment of the present invention provides a file calling method, including: receiving a file calling instruction sent by a service system, wherein the file calling instruction carries a file identifier of a file to be called;
determining the version corresponding to the file to be called according to the file identification;
determining search path information corresponding to the file to be called according to the version;
sequentially searching in the project files according to the node sequence of the search path information until a target file which is the same as the file identifier of the file to be called is obtained, wherein the project files are a plurality of files related to the service system;
and sending the target file to the service system.
Optionally, the version corresponding to the search path information is associated with the version to which the lowest level node of the search path information belongs; the method further comprises the following steps:
acquiring a newly input file, and determining a first target version to which the newly input file belongs;
determining first search path information corresponding to the first target version;
and storing the newly input file to the lowest level node of the first search path information.
Optionally, the method further includes:
if the newly input file is not matched with the corresponding version, determining a second target version to which the newly input file belongs;
updating the related search path information according to the relationship between the second target version and the existing version;
and storing the newly input file to the lowest level node of the search path information corresponding to the second target version.
Optionally, a version folder is created corresponding to each node for searching the path information; the method further comprises the following steps:
and storing the newly input file into a version folder corresponding to the node.
Optionally, the method further includes:
distributing a file identifier for the file at each node in the project file, wherein the file identifier comprises a version, a node level and a file identifier of a node at the upper level;
and respectively determining search path information corresponding to each version according to the node level and the file identifier of the upper-level node.
Optionally, the method further includes:
receiving a version switching request, wherein the version switching request comprises a third target version to be called;
and switching the configuration path to the search path information corresponding to the third target version according to the version switching request.
Optionally, after sending the target file to the service system, the method further includes:
acquiring a calling result of the service system after calling the target file;
and sending the calling result to a display terminal for display.
Optionally, the version corresponding to the file to be called is determined according to the file identifier, where the version is at least one of a language version, an area version, and a terminal model version.
In a second aspect, an embodiment of the present invention provides a file invoking device, including:
the touch control module is used for receiving a file calling instruction sent by a service system, wherein the file calling instruction carries a file identifier of a file to be called;
the processing module is used for determining the version corresponding to the file to be called according to the file identifier;
the processing module is further used for determining search path information corresponding to the file to be called according to the version;
the processing module is further configured to sequentially search in a project file according to the node sequence of the search path information until a target file identical to the file identifier of the file to be called is obtained, where the project file is a plurality of files associated with the service system;
and the sending module is used for sending the target file to the service system.
Optionally, the version corresponding to the search path information is associated with the version to which the lowest level node of the search path information belongs, and the touch module is further configured to:
acquiring a newly input file, and determining a first target version to which the newly input file belongs;
determining first search path information corresponding to the first target version;
and storing the newly input file to the lowest level node of the first search path information.
In a third aspect, an embodiment of the present invention provides a file calling device, including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the memory-stored computer-executable instructions causes the at least one processor to perform the file call method of any of the first aspects.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the file calling method according to any one of the first aspects is implemented.
The embodiment of the invention provides a file calling method, a file calling device and file calling equipment, wherein after the scheme is adopted, a piece of search path information can be correspondingly configured for each version of file, when a business system calls a target file, the version corresponding to the target file is determined according to the identification of the target file, then the corresponding files are sequentially searched according to the search path information corresponding to the version until the target file is found, and the target file is sent to the business system for calling of the business system, the business system does not need to determine the storage position of the target file in advance any more, the calling program is simplified, the calling time of the file is reduced, and the running speed of the business system is further improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is an application schematic diagram of a file calling method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a file calling method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an application of a game version provided by an embodiment of the present invention;
fig. 4 is a schematic diagram of application of version switching according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a planning structure of installation packages of different versions according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a directory structure of each version node according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a file calling apparatus according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a hardware structure of a file call device 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.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The secondary development of the software is developed aiming at the personalized requirements of customers on the basis of the existing software products. When the existing product functions cannot meet the requirements of customers or need to be in butt joint with other software to realize data exchange and transmission, secondary development is needed to realize corresponding functions. In the secondary development process, the project file is a general name of all the related files, and specifically may include a source project file and a copy project file. The duplicate engineering files are obtained by directly developing on the basis of the source engineering files, and the duplicate engineering files are obtained by developing on the basis of the duplicate engineering files. In addition, the developed form may include a modification operation and an addition operation. For example, in the duplicate engineering file, the file E in the source engineering file may be modified to obtain the duplicate engineering file E +. And a duplicate engineering file F can be directly added to the duplicate engineering files.
However, regardless of the modification method, the modified copy project files and the source project files are distributed in the storage space in a scattered manner. Before calling a file, management personnel are required to manually store all files corresponding to the version to which the file belongs in a folder, so that paths of the files of the same version are unified. And then configuring a path of each file, returning the configured path of each file to the service system, and calling the corresponding file according to the configured path when the service system calls the file. If the versions need to be switched, the administrator needs to manually store the files corresponding to the new versions into a new folder, configure the path of each file of the new versions, and return the configured path of each file of the new versions to the service system. The manual operation is complicated, errors are easy to occur, the calling time of the file is prolonged, and the running speed of the service system is further reduced.
Aiming at the problems, the method aims to improve the accuracy of file calling and the efficiency of file calling, and further improves the running speed of a business system. According to the method and the device, different search path information is configured for the files of different versions, and then the files are automatically searched in the project file according to the search path information corresponding to the version to which the target file belongs, so that the accuracy rate of file calling is improved, and the efficiency of file calling is improved.
Fig. 1 is an application schematic diagram of a file calling method according to an embodiment of the present invention, as shown in fig. 1, including a processing server 101, a file database 102, and a service system server 103, where a service system is configured in the service system server 103, and is used for implementing a service function. In implementing a business function, various different files may need to be invoked, the files being stored in the file database 102. During the call, the processing server 101 is required to control the call of the implementation file from the file database 102 to the business system. For example, the service system may be an AAA game system, and the game system needs to call different versions of installation package files according to actual needs of the service during installation or startup, and the installation package files are stored in the file database 102. The processing server 101 is used to control the invocation of implementing the installation package file to the AAA game system. In addition, the service system may also be deployed in the processing server 101, that is, the service system may be an internal operating system in the processing server 101 or an external operating system outside the processing server 101.
The technical solution of the present invention will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 2 is a flowchart illustrating a file calling method according to an embodiment of the present invention, where the method according to the embodiment may be executed by the processing server 101. As shown in fig. 2, the method of this embodiment may include:
s201: and receiving a file calling instruction sent by a service system, wherein the file calling instruction carries a file identifier of a file to be called.
Specifically, different files may be needed in the operation process of the service system. When a file is needed to be used, a file calling instruction may be sent to the processing server, where the file calling instruction may include a file identifier of the file to be called. The processing server may look up the corresponding file according to the file identifier.
S202: and determining the version corresponding to the file to be called according to the file identification.
Specifically, in the operation process of the business system, files of different versions may need to be acquired. For example, during game installation, the installation package may involve versions corresponding to different languages. Can be Thai edition, English edition, complex edition, Japanese edition, or simplified edition.
As shown in fig. 3, which is an application schematic diagram of a game version provided in an embodiment of the present invention, in the embodiment, a mini game is provided, and the game corresponds to an installation package of four versions, i.e., a computer version, an Android version, a Mac version, and an iPad version. After the version required to be installed by the user is determined, the installation package of the version can be correspondingly obtained. For example, if the user triggers an Android button, the Android game installation package is acquired.
In addition, there are various ways to determine the version of the target file. For example, each file may be assigned a version identifier, and the version corresponding to the file may be determined by the identifier. In addition, the version of the file can be directly represented by a naming rule. For example, if a file belongs to version G, the names of the files belonging to that version may each be configured in the format of "G-XXX". After the identifier of the version is configured, the version of the target file can be determined correspondingly according to the configured identifier directly at the later stage.
S203: and determining the search path information corresponding to the file to be called according to the version.
Specifically, in order to improve the efficiency of searching for the file, a piece of search path information may be configured in advance for each version. The search path information comprises a file search sequence of the corresponding version. There may be multiple nodes in the lookup path information, and each node may represent a version. Some versions are obtained by secondary development directly on the basis of source engineering files. Some versions are obtained by secondary development on the basis of the copy engineering file, namely, the versions are obtained by secondary development on the basis of other versions. When determining the version corresponding to the searched path information, since the last node is the latest updated version, the version corresponding to the last node may be determined as the version corresponding to the searched path information. There may be one file or multiple files at the node corresponding to each version. In both a file and a plurality of files, as long as the nodes where the files are located are the same, the corresponding search path information is also the same.
In addition, in order to improve the accuracy and efficiency of searching the target file, the versions and the search path information may be in one-to-one correspondence. After the version to which the target file belongs is determined, only the file corresponding to the search path information of the version to which the target file belongs needs to be searched, and the files corresponding to other search path information do not need to be searched.
S204: and searching in sequence in the project files according to the node sequence of the search path information until obtaining a target file with the same file identification as the file to be called, wherein the project files are a plurality of files associated with the service system.
Specifically, after the search path information corresponding to the version is determined, the files may be sequentially searched in the project file according to the node sequence of the search path information and the identifier of the file to be searched until the target file identical to the file identifier of the file to be called is obtained. The number of nodes for searching the path information is variable, the minimum number is two, and each node corresponds to the version after one modification.
The modified version can correspondingly store a copy engineering file, and the copy engineering file can be a file obtained by modification on the basis of a file existing in the previous version or a newly added file.
In addition, the file name of the file modified on the basis of the base file existing in the previous version may be identical to the file name of the base file of the previous version. When the search path information is configured, the path information can be configured according to the sequence from the node which is updated latest to the node corresponding to the source engineering file, and the file which is searched each time is the latest updated file. If the names of the files are different, the path information can be configured according to the sequence from the node which is updated latest to the node which corresponds to the source engineering file when the path information is configured and searched, and can also be configured according to the sequence from the node which corresponds to the source engineering file to the node which is updated latest.
S205: and sending the target file to the service system.
Specifically, after the real target file is found according to the information of the target file, the target file can be directly sent to the service system, and the service system can directly call the target file after receiving the target file. For example, the actual target file may be located based on the identification or name of the target file.
In addition, if the business system requests multiple target files at the same time, the arrival time of each target file at the business system may be different. In order to improve the operation efficiency of the service system, the service system may sequence the arriving target files in the calling order, and if most of the arriving target files are files that need to be called initially, the arrived target files may be called first. That is, the arrival of the destination file is waited for while executing the destination file that has arrived.
After the scheme is adopted, one piece of search path information can be correspondingly configured for each version, when the business system calls the target file, only the version corresponding to the target file needs to be determined, then the corresponding files are sequentially searched according to the search path information corresponding to the version until the target file is found, and the target file is sent to the business system for the business system to call.
Based on the method of fig. 2, the present specification also provides some specific embodiments of the method, which are described below.
In addition, in a specific embodiment, the version corresponding to the search path information is associated with the version to which the lowest level node of the search path information belongs, and the method may further include:
the method comprises the steps of obtaining a newly input file and determining a first target version to which the newly input file belongs. And determining first search path information corresponding to the first target version. And storing the newly input file to the lowest level node of the first search path information.
Specifically, each node corresponds to one version, and a plurality of associated nodes can form one piece of search path information. When the search path information is formed, each node may include a version and a node identifier, the node identifier includes a hierarchy of its previous node and its own node, and the search path information of each version may be determined according to the hierarchy of its previous node and its own node. The highest level is the level of the node where the source engineering file is located, and the lowest level is the node corresponding to the latest updated version file.
When a newly input file is acquired, the version to which the file belongs may be determined first according to the file identifier, and if it can be determined that the newly input file belongs to the existing version, the search path information of the version to which the file belongs, that is, the first search path information, may be directly determined. And then storing the newly input file to the first search path information.
In addition, in a specific embodiment, the method may further include:
and if the newly input file is not matched with the corresponding version, determining a second target version to which the newly input file belongs.
Specifically, when a new input file is acquired, the version of the file needs to be determined first, then whether the file belongs to an existing version is determined according to the version of the file, and when the new input file does not match the corresponding version, it is indicated that the new input file does not belong to the existing version, and a new version node needs to be created to store the new input file.
And updating the related search path information according to the relationship between the second target version and the existing version.
Specifically, after determining the second target version of the newly input file, the relationship between the version and the existing version needs to be determined. For example, the version may be directly developed and generated on the source engineering file, or may be generated by refining the existing version, for example, refining the installation package in the version of southeast asia to obtain the installation package in the version of southeast asia.
After the relationship between the version and the existing version is determined, the search path information may be updated according to the determined relationship. For example, if the version is developed and generated directly on the basis of the source engineering file, a new node representing the version may be added behind the node corresponding to the source engineering file, and the search path information of the version is configured as follows: and representing the node of the version and the node corresponding to the source project file. If the version is generated by refining on the basis of the existing version, a new node corresponding to the version can be added behind the node corresponding to the existing version, and then the search path information of the existing version is modified into: the new node corresponding to the version, the node corresponding to the existing version and the node corresponding to the source engineering file.
And storing the newly input file to the lowest level node of the search path information corresponding to the second target version.
Specifically, if the level of the node corresponding to the source engineering file is set as the highest level, after the search path information corresponding to the second target version is determined, the newly input file needs to be placed at the node of the lowest level of the search path information, that is, the newly created node. And when the searching is carried out subsequently, searching is carried out sequentially from the lowest level node to the highest level node, and the searched files are the latest updated files each time.
In addition, in a specific embodiment, the creating a version folder for each node that searches for path information further includes:
and storing the newly input file into a version folder corresponding to the node.
Specifically, in order to manage files, a file corresponding to each node is stored in one folder.
In addition, in a specific embodiment, the method may further include:
and allocating a file identifier for the file at each node in the project file, wherein the file identifier comprises a version, a node level and a file identifier of a node at the upper level.
And respectively determining search path information corresponding to each version according to the node level and the file identifier of the upper-level node.
Specifically, the hierarchical relationship between the versions is embodied by nodes. That is, the hierarchical relationship between the files corresponding to the versions may also be embodied by the nodes. When creating nodes corresponding to versions, a file identifier needs to be assigned to a file at each node. There may be one or more files at each node. Files at the same node, whether one or more, have a uniform file identification.
In addition, the file identification also comprises a corresponding version, a level of the node where the file identification is located and the file identification of the corresponding upper-level node. The incidence relation between the nodes can be determined through the levels of the nodes and the file identifications of the corresponding nodes at the upper level, and then the search path information corresponding to each version is created according to the incidence relation between the nodes.
In addition, in a specific embodiment, the method may further include:
and receiving a version switching request, wherein the version switching request comprises a third target version to be called. And switching the configuration path to the search path information corresponding to the third target version according to the version switching request.
Specifically, as shown in fig. 4, an application diagram of version switching provided in the embodiment of the present invention is shown, in this embodiment, the current version is a XXXX game installation package of a japanese regional version, and a user or a manager may manually trigger a corresponding switch button when he or she wants to switch to the XXXX game installation package of a south-east thailand version. And the processing server correspondingly switches according to the version switching request generated by triggering the switching button.
In addition, in a specific embodiment, after sending the target file to the business system, the method further includes:
and acquiring a calling result after the service system calls the target file.
And sending the calling result to a display terminal for display.
Specifically, after the service system calls the target file, the call may be successful or may fail. In order to inform the administrator of the calling result in time, the calling result can be displayed on a display terminal. The calling failure can be displayed on the display terminal, and the calling success can also be displayed on the display terminal. If the calling is successful, the result generated after the calling can be displayed between the display terminals.
In addition, in a specific embodiment, the determining, according to the file identifier, a version corresponding to the file to be called is at least one of a language version, an area version, and a terminal model version.
In particular, versions may include different categories, each of which may in turn include a different type. For example, the category of the version may be a language version, a region version, a terminal model version, and the like. When the version type is a language version, the language version may include different types such as a chinese version, a japanese version, a tai version, and an english version. The other types are similar to the language version, and when the version type is a regional version, the regional version can include different types such as a Chinese regional version, a Thailand regional version, a Japanese regional version and the like. When the version type is a terminal model version, the terminal model version may include different types such as an android version, an apple version, a Windows version, and the like.
In addition, a plurality of different versions can be combined to form a new version. For example, the region version and the language version may be combined to form a region language version. For example, a southeast asia version of thai, southeast asia version of english, asia version of japanese, or asia version of chinese, etc. may be formed.
In addition, file identification may be used to distinguish versions. Therefore, the file identifiers can correspond to the versions one to one, that is, one version uniquely corresponds to one file identifier. The representation of the file identifier may be various. For example, the characters may be represented by at least one of capital letters, lowercase letters, arabic numerals, and roman numerals. In a specific example, the language version may correspond to the file identifier a, the area version may correspond to the file identifier B, and the terminal model version may correspond to the file identifier C. The language version can also comprise a Chinese version, a Japanese version, a Thai version and an English version. The Chinese version may correspond to the file identifier A1, the Japanese version may correspond to the file identifier A2, the Thai version may correspond to the file identifier A3, and the English version may correspond to the file identifier A4.
When the area language version is formed by combining the area version and the language version, the file identifier BA may be used to correspond to the area language version. The regional language versions may include the southeast asia thai version, the southeast asia english version, the asia japanese version, and the asia chinese version. The southeast Asia Thai version may correspond to the file identification B1A3, the southeast Asia English version may correspond to the file identification B1A4, the Asian Japanese version may correspond to the file identification B2A2, and the Asian Chinese version may correspond to the file identification B2A 1.
As shown in fig. 5, a schematic diagram of a planning structure of installation packages of different versions is provided in the embodiment of the present application, in which an installation package of a japanese regional version and an installation package of a southeast asian regional version are developed on the basis of source engineering, and then an installation package of a southeast asian english version and an installation package of a southeast asian taiwen version are developed on the installation package of the southeast asian regional version.
As shown in fig. 6, a directory structure diagram of each version node is provided in the embodiment of the present invention, in this embodiment, there are a plurality of node information, project node information includes a source project file, project _ as node information includes a duplicate project file related to a southeast asian region version, project _ as _ en node information includes a duplicate project file related to a southeast asian region english version, project _ as _ th node information includes a duplicate project file related to a southeast asian region thai version, and project _ jp node information includes a duplicate project file related to a japan region version.
After the node information is determined, the search path information of the version corresponding to the node may be generated according to the node information. For example, in this embodiment, four pieces of search path information may be generated, which are respectively an english version in southeast asia, a thai version in southeast asia, a regional version in southeast asia, and a japanese version, specifically as follows:
id 1: project _ as _ en, Project _ as, Project ]// southeast Asia English version;
id 2: project _ as _ th, Project _ as, Project ]// Thai version of southeast Asia;
id 3: project _ as _ th, Project _ as// southeast Asia region version;
id 4: [ Project _ jp, Project ]// Japanese version.
As shown in fig. 6, when a new version file is formed, the base file may be modified on the basis of the original version base file. For example, when a version file of the south-east asian thai version is formed, modification may be performed on the basis of the base file script1 of the south-east asian region version to obtain a new version file. In order to record the new version file, the new version file is modified on the basis of the base file, and the name of the new version file may be named as script 1. And adding a node of the version of the southeast Asia Thai version behind the node of the version of the southeast Asia region, and storing a new version script1 at the node to form new node information. When the search path information of the new version is configured, the configuration can be performed according to the sequence from the node corresponding to the new version file to the node corresponding to the source engineering file, so that the file called by the service system each time is the latest modified file corresponding to the version.
Based on the same idea, an embodiment of the present specification further provides a device corresponding to the foregoing method, and as shown in fig. 7, a schematic structural diagram of a file invoking device provided in the embodiment of the present invention may include:
the touch module 701 is configured to receive a file call instruction sent by a service system, where the file call instruction carries a file identifier of a file to be called.
And the processing module 702 is configured to determine, according to the file identifier, a version corresponding to the file to be called.
The processing module 702 is further configured to determine, according to the version, search path information corresponding to the file to be called.
The processing module 702 is further configured to sequentially search for project files according to the node sequence of the search path information until a target file that is the same as the file identifier of the file to be called is obtained, where the project files are multiple files associated with the service system.
A sending module 703, configured to send the target file to the service system.
In addition, in a specific embodiment, a version corresponding to the search path information is associated with a version to which a lowest level node of the search path information belongs, and the touch module may be configured to:
the method comprises the steps of obtaining a newly input file and determining a first target version to which the newly input file belongs.
And determining first search path information corresponding to the first target version.
And storing the newly input file to the lowest level node of the first search path information.
In addition, in a specific embodiment, the touch module may be further configured to:
and if the newly input file is not matched with the corresponding version, determining a second target version to which the newly input file belongs.
And updating the related search path information according to the relationship between the second target version and the existing version.
And storing the newly input file to the lowest level node of the search path information corresponding to the second target version.
In addition, in a specific embodiment, each node that searches for path information creates a version folder, and the processing module is further configured to:
and storing the newly input file into a version folder corresponding to the node.
In addition, in a specific embodiment, the processing module is further configured to:
and allocating a file identifier for the file at each node in the project file, wherein the file identifier comprises a version, a node level and a file identifier of a node at the upper level.
And respectively determining search path information corresponding to each version according to the node level and the file identifier of the upper-level node.
In addition, in a specific embodiment, the touch module may further be configured to:
and receiving a version switching request, wherein the version switching request comprises a third target version to be called.
And switching the configuration path to the search path information corresponding to the third target version according to the version switching request.
In addition, in a specific embodiment, the touch module may further be configured to:
and acquiring a calling result after the service system calls the target file.
And sending the calling result to a display terminal for display.
In addition, in a specific embodiment, the determining, according to the file identifier, a version corresponding to the file to be called is at least one of a language version, an area version, and a terminal model version.
The apparatus provided in the embodiment of the present invention may implement the method in the embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 8 is a schematic diagram of a hardware structure of a file call device according to an embodiment of the present invention. As shown in fig. 8, the apparatus 800 provided in this embodiment includes: at least one processor 801 and a memory 802. The processor 801 and the memory 802 are connected by a bus 803.
In a specific implementation, at least one processor 801 executes computer-executable instructions stored by the memory 802, so that at least one processor 801 executes the method in the above-described method embodiments.
For a specific implementation process of the processor 801, reference may be made to the above method embodiments, which have similar implementation principles and technical effects, and details of this embodiment are not described herein again.
In the embodiment shown in fig. 8, it should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.
The memory may comprise high speed RAM memory and may also include non-volatile storage NVM, such as at least one disk memory.
The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The embodiment of the invention also provides a computer-readable storage medium, wherein a computer execution instruction is stored in the computer-readable storage medium, and when a processor executes the computer execution instruction, the file calling method of the method embodiment is realized.
The computer-readable storage medium may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the readable storage medium may also reside as discrete components in the apparatus.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (12)
1. A file calling method, comprising:
receiving a file calling instruction sent by a service system, wherein the file calling instruction carries a file identifier of a file to be called;
determining the version corresponding to the file to be called according to the file identification;
determining search path information corresponding to the file to be called according to the version;
sequentially searching in the project files according to the node sequence of the search path information until a target file which is the same as the file identifier of the file to be called is obtained, wherein the project files are a plurality of files related to the service system;
and sending the target file to the service system.
2. The method according to claim 1, wherein the version corresponding to the search path information is associated with the version to which the lowest level node of the search path information belongs; the method further comprises the following steps:
acquiring a newly input file, and determining a first target version to which the newly input file belongs;
determining first search path information corresponding to the first target version;
and storing the newly input file to the lowest level node of the first search path information.
3. The method of claim 2, further comprising:
if the newly input file is not matched with the corresponding version, determining a second target version to which the newly input file belongs;
updating the related search path information according to the relationship between the second target version and the existing version;
and storing the newly input file to the lowest level node of the search path information corresponding to the second target version.
4. The method according to any one of claims 2-3, wherein each node for searching path information corresponds to creating a version folder; the method further comprises the following steps:
and storing the newly input file into a version folder corresponding to the node.
5. The method according to any one of claims 1-3, further comprising:
distributing a file identifier for the file at each node in the project file, wherein the file identifier comprises a version, a node level and a file identifier of a node at the upper level;
and respectively determining search path information corresponding to each version according to the node level and the file identifier of the upper-level node.
6. The method according to any one of claims 1-3, further comprising:
receiving a version switching request, wherein the version switching request comprises a third target version to be called;
and switching the configuration path to the search path information corresponding to the third target version according to the version switching request.
7. The method according to any of claims 1-3, further comprising, after sending the object file to the business system:
acquiring a calling result of the service system after calling the target file;
and sending the calling result to a display terminal for display.
8. The method according to any one of claims 1 to 3, wherein the version corresponding to the file to be called is determined according to the file identifier, and the version is at least one of a language version, an area version, and a terminal model version.
9. A file calling apparatus, comprising:
the touch control module is used for receiving a file calling instruction sent by a service system, wherein the file calling instruction carries a file identifier of a file to be called;
the processing module is used for determining the version corresponding to the file to be called according to the file identifier;
the processing module is further used for determining search path information corresponding to the file to be called according to the version;
the processing module is further configured to sequentially search in a project file according to the node sequence of the search path information until a target file identical to the file identifier of the file to be called is obtained, where the project file is a plurality of files associated with the service system;
and the sending module is used for sending the target file to the service system.
10. The apparatus of claim 9, wherein the version corresponding to the search path information is associated with a version to which a lowest level node of the search path information belongs, and the touch module is further configured to:
acquiring a newly input file, and determining a first target version to which the newly input file belongs;
determining first search path information corresponding to the first target version;
and storing the newly input file to the lowest level node of the first search path information.
11. A file calling apparatus, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the memory-stored computer-executable instructions causes the at least one processor to perform the file call method of any of claims 1 to 8.
12. A computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a processor, implement the file call method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010147215.1A CN111338689B (en) | 2020-03-05 | 2020-03-05 | File calling method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010147215.1A CN111338689B (en) | 2020-03-05 | 2020-03-05 | File calling method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111338689A true CN111338689A (en) | 2020-06-26 |
| CN111338689B CN111338689B (en) | 2023-12-29 |
Family
ID=71182182
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010147215.1A Active CN111338689B (en) | 2020-03-05 | 2020-03-05 | File calling method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111338689B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988810A (en) * | 2021-03-08 | 2021-06-18 | 网易（杭州）网络有限公司 | Information searching method, device and equipment |
| CN113343030A (en) * | 2021-07-07 | 2021-09-03 | 湖南快乐阳光互动娱乐传媒有限公司 | Data processing method and device, electronic equipment and computer readable storage medium |
| CN114020694A (en) * | 2021-10-19 | 2022-02-08 | 北京五八信息技术有限公司 | Header file address acquisition method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050144599A1 (en) * | 2003-12-26 | 2005-06-30 | Microsoft Corporation | Source server |
| CN105630779A (en) * | 2014-10-27 | 2016-06-01 | 杭州海康威视系统技术有限公司 | Hadoop distributed file system based small file storage method and apparatus |
| CN107526777A (en) * | 2017-07-21 | 2017-12-29 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus handled based on version number file |
| CN110321325A (en) * | 2019-06-21 | 2019-10-11 | 腾讯科技（深圳）有限公司 | File inode lookup method, terminal, server, system and storage medium |
-
2020
- 2020-03-05 CN CN202010147215.1A patent/CN111338689B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050144599A1 (en) * | 2003-12-26 | 2005-06-30 | Microsoft Corporation | Source server |
| CN105630779A (en) * | 2014-10-27 | 2016-06-01 | 杭州海康威视系统技术有限公司 | Hadoop distributed file system based small file storage method and apparatus |
| CN107526777A (en) * | 2017-07-21 | 2017-12-29 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus handled based on version number file |
| CN110321325A (en) * | 2019-06-21 | 2019-10-11 | 腾讯科技（深圳）有限公司 | File inode lookup method, terminal, server, system and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988810A (en) * | 2021-03-08 | 2021-06-18 | 网易（杭州）网络有限公司 | Information searching method, device and equipment |
| CN113343030A (en) * | 2021-07-07 | 2021-09-03 | 湖南快乐阳光互动娱乐传媒有限公司 | Data processing method and device, electronic equipment and computer readable storage medium |
| CN114020694A (en) * | 2021-10-19 | 2022-02-08 | 北京五八信息技术有限公司 | Header file address acquisition method and device, electronic equipment and storage medium |
| CN114020694B (en) * | 2021-10-19 | 2022-10-28 | 北京五八信息技术有限公司 | Header file address acquisition method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111338689B (en) | 2023-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111338689B (en) | File calling method, device and equipment | |
| CN111182089B (en) | Container cluster system, method and device for accessing big data assembly and server | |
| US7581047B2 (en) | Usage of keyboard driver in extensible firmware interface for adding new hot keys at firmware level | |
| US20220179642A1 (en) | Software code change method and apparatus | |
| CN111143723A (en) | Page jump method and device, electronic equipment and storage medium | |
| CN109669741B (en) | Language switching method, server and storage medium for terminal application dynamic document | |
| CN108776587B (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN104216724A (en) | Method and system for updating network application program interface | |
| CN113141405A (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN110716786B (en) | Page display method, system and storage medium | |
| EP4060484A1 (en) | Control method and control device for enabling operations of application program in multiple systems | |
| CN109117351B (en) | Front-end display implementation method for Docker container cloud host and Dashboard | |
| CN113132241B (en) | ACL template dynamic configuration method and device | |
| CN112433741B (en) | Page processing method, device and system, electronic equipment and storage medium | |
| CN112988810B (en) | Information searching method, device and equipment | |
| CN112350856B (en) | Distributed service sign-off method and equipment | |
| CN111026613B (en) | Log processing method and device | |
| CN111181836B (en) | Message pushing method and device | |
| CN113821249A (en) | Project development configuration method and device, electronic equipment and readable storage medium | |
| CN112948264A (en) | Test task execution method, device, system, storage medium and electronic device | |
| CN111443920A (en) | Frame migration method and device | |
| CN111459911A (en) | Service data processing method and device | |
| CN112558975B (en) | Method and device for switching codes of components, electronic equipment and readable storage medium | |
| CN111767104B (en) | Language type switching method and device, computer equipment and storage medium | |
| CN112565414B (en) | Data downloading method, device, equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |