Project directory download method and related apparatus

Abstract

The embodiment of the present application provides a project directory downloading method and related device, wherein the project directory downloading method is suitable for a server and comprises the following steps: obtaining a first target directory according to a directory name; sending the first target directory to a client according to a first downloading path between a server first directory of the first target directory and a client first directory which is established in advance, so that the client establishes corresponding client directories under the client first directory; and when a configuration command obtained according to a configuration file of the corresponding first target directory is received from the client, sending a configuration level server directory to the client according to the configuration command. It can be seen that the project directory downloading method and related device provided by the embodiment of the present application can reduce the work difficulty in the development process on the basis of simplifying the downloading path.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a method and related apparatus for downloading a project directory. Background Technology

[0002] In scenarios such as integrated circuit design or software development, each developer or team (client) is responsible for the design of each module. For the developer or team responsible for the module, each module can be called a project, while on the server side it is represented as a directory (for ease of description, this article will refer to it as a directory). The relationship between the various levels of directories corresponds to the relationship between the various modules, such as first-level directory, second-level directory, third-level directory, etc. At the same time, the directory includes the directory body and the files that should belong to the directory.

[0003] Of course, in practical use, to simplify the download process and avoid download path errors due to different paths of lower-level directories, lower-level directories (such as second-level directories) belonging to the same higher-level directory (such as the first-level directory) are all placed in the same directory. In this way, when downloading a directory, only the entire higher-level directory needs to be downloaded. However, since different higher-level directories (such as first-level directory 1, first-level directory 2, ..., first-level directory n) may use the same lower-level directory (such as second-level directory 1), it is necessary to store the corresponding lower-level directory under each higher-level directory. Moreover, when it is necessary to modify the lower-level directory, it is necessary to modify the corresponding lower-level directories under each higher-level directory. This not only increases the workload of modification, but also easily leads to omissions in modification and subsequent processing errors, making the development process more difficult.

[0004] It is evident that simplifying the download path while reducing the difficulty of the development process has become a pressing technical problem that needs to be solved in this field. Summary of the Invention

[0005] In view of this, this application provides a project directory download method to reduce the difficulty of the development process by simplifying the download path.

[0006] To achieve the above objectives, the embodiments of this application provide the following technical solutions:

[0007] In a first aspect, embodiments of this application provide a method for downloading a project directory, applicable to a server, including:

[0008] Obtain the directory name, and obtain the first target directory based on the directory name. The first target directory includes the server directories at all levels corresponding to the directory name in the server.

[0009] Based on the first download path between the server-level directory of the first target directory and the pre-established client-level directory, the first target directory is sent to the client through the first download path, so that the client can establish corresponding client-level directories under the client-level directory;

[0010] When a configuration command obtained from a configuration file corresponding to the first target directory is received from a client, a second download path is established for the configuration level server directory and the configuration level client directory based on the second path information in the configuration command. The configuration level server directory is then sent to the client through the second download path. The configuration level client directory is a directory established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory.

[0011] Secondly, embodiments of this application provide a method for downloading a project directory, applicable to a client, including:

[0012] Create a client-side first-level directory and send the directory name of the client-side first-level directory so that the server can obtain the first target directory corresponding to the directory name. The first target directory includes all levels of server directories corresponding to the directory name.

[0013] Receive the first target directory sent through the first download path between the server-level directory and the client-level directory, and create corresponding client-level directories under the client-level directory;

[0014] When parsing the configuration file corresponding to the first target directory and no sub-configuration file information is obtained, a configuration command is sent, and the configuration level server directory in the configuration command is received through the second download path. The second download path is the path between the configuration level server directory and the configuration level client directory established according to the second path information in the configuration command. The configuration level client directory is the client's various levels of directories established under the client's first-level directory. The configuration level server directory is a directory different from the first target directory.

[0015] Thirdly, embodiments of this application provide a project directory download device, suitable for servers, comprising:

[0016] The directory name acquisition module is adapted to acquire a first target directory based on the directory name, wherein the first target directory includes server directories at various levels corresponding to the directory name in the server;

[0017] The first target directory sending unit is adapted to send the first target directory to the client through the first download path according to the first download path between the server-level directory of the first target directory and the pre-established client-level directory, so that the client can establish corresponding client-level directories under the client-level directory;

[0018] The configuration level server directory sending unit is adapted to, when receiving a configuration command sent by a client based on a configuration file corresponding to the first target directory, establish a second download path for the configuration level server directory and the configuration level client directory based on the second path information in the configuration command, and send the configuration level server directory to the client through the second download path, wherein the configuration level client directory is a directory established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory.

[0019] Fourthly, embodiments of this application provide a project catalog download device, applicable to a client, including:

[0020] The directory name sending unit is adapted to create a client-level directory and send the directory name of the client-level directory so that the server can obtain a first target directory corresponding to the directory name. The first target directory includes server-level directories corresponding to the directory name.

[0021] The first target directory receiving unit is adapted to receive the first target directory sent through the first download path between the server-level directory and the client-level directory of the first target directory, and to establish corresponding client-level directories under the client-level directory;

[0022] The configuration command sending unit is adapted to send a configuration command when, after parsing the configuration file corresponding to the first target directory, no sub-configuration file information is obtained, and to receive the configuration level server directory in the configuration command through a second download path. The second download path is a path between the configuration level server directory and the configuration level client directory established according to the second path information in the configuration command. The configuration level client directory is the client's various levels of directories established under the client's first-level directory. The configuration level server directory is a directory different from the first target directory.

[0023] Fifthly, embodiments of this application provide a server that stores a project directory download program to implement the project directory download method as described in the first aspect.

[0024] Sixthly, embodiments of this application provide a client that stores a project directory download program to implement the project directory download method as described in the second aspect.

[0025] In a seventh aspect, embodiments of this application also provide a storage medium storing a project directory download program to implement the project directory download method as described in the first or second aspect.

[0026] Compared with the prior art, the technical solution of the embodiments of the present invention has the following advantages:

[0027] The project directory download method provided in this application first obtains a directory name, then obtains a first target directory based on the directory name. Next, based on a first download path between the server-level directory of the first target directory and a pre-established client-level directory, the first target directory is sent to the client via the first download path. This causes the client to create corresponding client-level directories under the client-level directory. Furthermore, when a configuration command obtained from a configuration file corresponding to the first target directory is received from the client, a second download path is further established based on the second path information in the configuration command, connecting a configuration-level server directory and a configuration-level client directory. The configuration-level server directory is then sent to the client via the second download path. Here, the configuration-level client directory is a directory created under the client-level directory, and the configuration-level server directory is a directory different from the first target directory. It can be seen that the project directory download method provided in this application not only downloads the first target directory to a pre-established client-level directory but also enables the determination and download of configuration-level server directories that do not belong to the first target directory using configuration files corresponding to the first target directory.

[0028] As can be seen, by setting a configuration file corresponding to the first target directory and specifying the second download paths for the configuration level server directory and configuration level client directory within the configuration file, the configuration level server directory can be retrieved based on this configuration file. This eliminates the need to set related configuration level server directories within the first target directory, allowing the configuration level server directory to be set independently of other related directories without requiring multiple copies. This satisfies the download requirements for the same configuration level server directory across different high-level directories. When developing a new version of the configuration level server directory, only this single directory needs to be developed, and the configuration files in the first target directory (and other related directories) need to be modified to point to the new configuration level server directory, thus enabling development of the project directory and reducing the difficulty of modifying project directories. Furthermore, each directory exists only once on the server, saving storage resources. Maintaining only the configuration file ensures correct file downloads, reducing the maintenance costs of inter-directory relationships and the probability of download errors. Finally, the configuration files can be maintained separately by different developers or teams, transforming centralized directory management into decentralized configuration file management, which is beneficial for collaborative development among teams. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0030] Figure 1 This is a diagram illustrating a project directory storage and download process.

[0031] Figure 2 A diagram illustrating another method of storing and downloading project directories;

[0032] Figure 3 A flowchart illustrating the project directory download method provided in this application embodiment;

[0033] Figure 4 A schematic diagram of the directory storage structure of the server for the project directory download method provided in the embodiments of this application;

[0034] Figure 5 A schematic diagram of the configuration file structure for the project directory download method provided in this application embodiment;

[0035] Figure 6A schematic diagram of the structure of the sub-configuration file of the project directory download method provided in the embodiments of this application;

[0036] Figure 7 A block diagram of the project catalog download device provided in the embodiments of this application;

[0037] Figure 8 Another block diagram of the project catalog download device provided in the embodiments of this application. Detailed Implementation

[0038] It is evident that existing technologies present a technical challenge: how to simplify the download path while reducing the complexity of the development process.

[0039] To better understand the project directory download issue, please refer to [link / reference]. Figure 1 and Figure 2 , Figure 1 This is a diagram illustrating a project directory storage and download process. Figure 2 This is a diagram illustrating another method of storing and downloading project directories.

[0040] like Figure 1 As shown, downloading directories and files from the server to the client requires downloading a directory or file to a specified path. For example, if the development team is responsible for project CHIP_A and needs to use IPs such as IP1 and IP2, then the content needs to be downloaded from the subdirectories IP1 and IP2 under the "IP" directory on the server. Additionally, files need to be downloaded from the "SOC" directory under the "projectA" directory in the "project" directory to the SOC directory on the client. This requires knowing the download path from the server's subdirectory IP1 to the client's IP1, the server's subdirectory IP2 to the client's IP2, and the download path from the server's "SOC" directory to the client's SOC directory.

[0041] In practice, as the number of directories and files increases, the download process becomes increasingly complex. For example, IP1 might need files located under IP2, and both IP1 and IP2 might need files located under IP3. If files are not downloaded to the correct paths, it can lead to program failures and other errors. Therefore, the team needs to manage the methods and processes for downloading files and directories to mitigate potential risks during the download phase.

[0042] To avoid download path errors due to different paths in lower-level directories, in practice, all lower-level directories (such as second-level directories) belonging to the same higher-level directory (such as a first-level directory) are placed under the same directory. Figure 2As shown, subdirectories IP1, IP2, and SOC_A, which are second-level directories, are all placed under CHIP_A, which is a first-level directory. This way, when downloading directories, only CHIP_A needs to be downloaded to the client. However, to ensure that each higher-level directory contains all its corresponding lower-level directories, i.e.... Figure 2 The method shown requires storing all corresponding lower-level directories under each higher-level directory (for example, another project CHIP_B also needs IP1, so the directory CHIP_B also stores the subdirectory IP1). Thus, when a lower-level directory needs to be modified, the corresponding lower-level directories under each higher-level directory need to be modified (modifying the subdirectory IP1 under the directory CHIP_A requires modifying the subdirectory IP1 under the directory CHIP_B as well). This not only increases the workload of modification, but also easily leads to omissions in modification, resulting in errors in subsequent processing, making the development process more difficult.

[0043] As can be seen, the above-mentioned methods for downloading project directories are either complex or difficult to implement. Therefore, how to simplify the download path while reducing the difficulty of the development process has become a technical problem that urgently needs to be solved in this field.

[0044] To address the aforementioned technical problems, this application provides a project directory download method to simplify the download path and reduce the difficulty of the development process.

[0045] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0046] Please refer to Figure 3 , Figure 3 This is a flowchart illustrating a project directory download method provided in an embodiment of this application.

[0047] like Figure 3 As shown in the embodiments of this application, the project directory download method includes:

[0048] Step S11: The client creates a client-level directory and sends the directory name of the client-level directory so that the server can obtain the first target directory corresponding to the directory name.

[0049] It's easy to understand that the project directory download process is divided into client and server. The client is the end that developers directly control and is used to develop the project directory, while the server contains all the project directories. Downloading the project directory is actually the process of downloading the project directory from the server to the client.

[0050] To enable the client to download the project directory, the target address for download needs to be set on the client, specifically the aforementioned client-level directory.

[0051] It is easy to understand that the client-side first-level directory mentioned in this article refers to the highest-level directory created by the client, which corresponds to an objectively existing storage location. It can be any level, not necessarily the first level.

[0052] After creating the client's first-level directory, send its directory name. It is important to note that the directory name of the first-level directory created at this time should correspond to the first target directory that needs to be obtained from the server, so as to ensure that the server can obtain the corresponding first target directory.

[0053] Furthermore, the project directories in the server correspond to the modules in the actual integrated circuit or software. For example, if the project includes module A, then there is a directory A in the server of this application. The various levels of the directory body of directory A and all the files in it together constitute module A. Updating the version of directory A on the client is equivalent to developing module A of the project.

[0054] Of course, the first target directory mentioned in this article refers to the directory stored on the server side that corresponds to the directory name of the client's first-level directory. It includes not only the directory at the corresponding level, but also the directories at all levels under that directory, including the directory bodies at each level and the files stored in each directory body. That is, the first target directory includes the server directories at all levels that correspond to the directory name.

[0055] It should be noted that the first target directory can be any level of directory stored on the server, not necessarily the highest level directory.

[0056] For details, please refer to Figure 4 , Figure 4 This is a schematic diagram of the directory storage structure of the server for the project directory download method provided in the embodiments of this application.

[0057] As shown in the figure, the server's directory includes the directory body at a higher directory level, directory 1 and directory 2. Under directory 1, there are the directory bodies at a lower directory level (subdirectories 1.1 and 1.2) and files (configuration files) belonging to directory 1. Under directory 2, there are files (configuration files) belonging to directory 2. Of course, there may be other directory bodies and files under both directory 1 and directory 2, which are shown in the figure with "...". It is also easy to understand that there may be multiple levels of directories under subdirectories, which are not shown in the figure.

[0058] Based on the foregoing description, depending on the directory to be downloaded, if the name of the first-level directory of the client is directory 1, then the first target directory is directory 1; if the name of the first-level directory of the client is subdirectory 1.1, then the first target directory is subdirectory 1.1.

[0059] Step S12: The server obtains the project name and retrieves the first target directory based on the project name.

[0060] After the client creates a client-level directory and sends the directory name, the server obtains the directory name and retrieves the first target directory based on the directory name. Of course, as mentioned above, the first target directory includes the server-level directory and the server-level directories (i.e., subdirectories and files) under the server-level directory. In this application, the directory is divided into the directory body and the files in the directory. Unless otherwise specified, the directory refers to the directory body and the files in the directory. In addition, the project directory in this application is synonymous with the directory.

[0061] The server receives the directory name sent by the client and uses it to obtain the first target directory.

[0062] Step S13: The server sends the first target directory to the client through the first download path, based on the first download path between the server-level directory of the first target directory and the pre-established client-level directory of the client.

[0063] After obtaining the first target directory, a first download path is constructed based on the server-level directory of the first target directory and the client-level directory established in step S11. Then, the first target directory is sent to the client through the first download path so that the client can establish client-level directories under the client-level directory.

[0064] In one specific implementation, the step of constructing the first download path may include:

[0065] First, receive the client-side first-level directory channel creation command and create a client-side first-level directory channel corresponding to the client-side first-level directory.

[0066] In addition to receiving the project name, you will also receive a client-side first-level directory channel creation command. Based on the client-side first-level directory channel creation command, a client-side first-level directory channel is established.

[0067] The client-side first-level directory channel is a channel created on the server to establish a download path to the client-side first-level directory. Only by creating a client-side first-level directory channel can the download path between the directory on the server and the client-side first-level directory be established. This is a management method for directory downloads.

[0068] Then, the server's first-level directory is set as the first source download address of the client's first-level directory channel, and the client's first-level directory is set as the first destination download address of the client's first-level directory channel. The first download path is constructed based on the first source download address and the first destination download address.

[0069] After establishing the client-side first-level directory channel, the two ends of the client-side first-level directory channel are determined, namely the server-side first-level directory and the client-side first-level directory, thus constructing the first download path.

[0070] In this way, only one client-level directory channel needs to be established to create the first download path between the first target directory and the client-level directory, and the first target directory can be sent to the client, thereby saving server resources.

[0071] Step S14: The client receives the first target directory sent through the first download path between the server-level directory and the client-level directory of the first target directory, and creates corresponding client-level directories under the client-level directory.

[0072] When the server sends the first target directory, the client receives the first target directory and creates corresponding client-level directories under the client's first-level directory.

[0073] Based on the preceding discussion, the client-side top-level directory has already been pre-established on the client. This client-side top-level directory is usually the working directory created by the development team. However, at this point, the client-side top-level directory does not have subdirectories or files. The server-side first target directory can be created level by level under the client-side top-level directory, and the files can be placed in the corresponding directories. For example, if the first target directory is directory A, which includes a second-level subdirectory B and a file C at the same level as directory B, and directory B contains file D, then after obtaining directory A by directory name, the server establishes the path between directory A and the client-side top-level directory, thereby sending file C to the client-side top-level directory, creating directory B, and sending file D to directory B.

[0074] As can be seen from the above examples, it is not necessary to create all levels of directories in the client's first-level directory in advance. If the server does not find the corresponding directory in the client's first-level directory when transferring the first target directory according to the path, it can directly create the directory and then put the file into the directory.

[0075] In this way, the client can obtain the client's first-level directory and all subsequent directories corresponding to the directory name from the server.

[0076] Step S15: The client determines whether it has obtained the configuration file corresponding to the first target directory. If so, it proceeds to step S16; otherwise, it proceeds to step S17.

[0077] The configuration file allows you to set the download path, which will then download directories from the server based on the specified path.

[0078] After the client receives the directories at each level of the first target directory, it further obtains the configuration file of the first target directory based on the relevant information and determines whether the corresponding configuration file has been obtained. If it has been obtained, it further executes step S16, that is, determines whether there is a sub-configuration file; otherwise, it executes step S17, that is, ends the project directory download, and the corresponding project directory has been obtained.

[0079] Depending on the different mappings between configuration files and directories, configuration files can be obtained in different ways, for example:

[0080] To obtain the corresponding configuration file more quickly, in one specific implementation, such as Figure 4 As shown, the configuration file is stored in the first target directory of the server. When the first target directory is sent to the client through the first download path, the configuration file in the first target directory is also sent to the client through the first download path. In this way, by directly placing the configuration file in the first target directory of the server, the configuration file can be obtained as part of the first target directory when the first target directory is obtained from the server. This eliminates the need to maintain a mapping table or other corresponding relationship information related to the location information of the configuration file. This allows for quick acquisition of the corresponding configuration file while saving the cost of maintaining the corresponding relationship.

[0081] Of course, in other embodiments, the configuration file can also be stored in other directories of the server. In this way, the configuration file to be retrieved can be determined based on the pre-set relevant information, and the corresponding configuration file can be retrieved based on the pre-set configuration file location information.

[0082] In another specific implementation, the configuration file can also be stored directly on the client, as long as the client can obtain the configuration file corresponding to the first target directory based on the pre-stored correspondence information.

[0083] The configuration file corresponds to the first target directory. It is easy to understand that in the specific implementation provided in this application, if the first target directory has a corresponding configuration file, then there is only one configuration file, and each configuration file corresponds to only one first target directory. Of course, the configuration file can also record the nesting relationship between the corresponding directory and other directories.

[0084] In one specific implementation, please refer to Figure 5 , Figure 5 This is a schematic diagram of the configuration file structure for the project directory download method provided in this application embodiment.

[0085] As shown in the figure, the configuration file may include:

[0086] Configure the client directory for the specified level, indicating where the directory should be downloaded;

[0087] Configure the server directory, indicating where to download from;

[0088] Version information, indicating the version in the download directory;

[0089] Sub-configuration file information, specifying the location of the sub-configuration file.

[0090] The existence of sub-configuration file information can be determined based on whether a sub-configuration file exists; version information may also not exist.

[0091] Step S16: The client determines whether it has obtained the sub-configuration file information of the configuration file. If yes, otherwise step S161 is executed; if yes, step S162 is executed.

[0092] After obtaining the configuration file, it is further determined whether the sub-configuration files can be obtained. This is mainly because in some cases, the client does not need the complete directory, but only the subdirectories or specific files under that directory. In this case, it is not necessary to download all the directories indicated in the configuration file. In this case, sub-configuration file information will be set in the configuration file so that the required subdirectories or files can be obtained based on the sub-configuration file information, thereby reducing the consumption of download resources.

[0093] Specifically, this can be achieved through parsing such as Figure 5 The configuration file shown is used to determine whether it includes sub-configuration file information.

[0094] If sub-configuration file information is found after parsing, proceed to step S162; otherwise, proceed to step S161.

[0095] Step S161: The client sends a configuration command.

[0096] After obtaining the configuration file in the first target directory, the configuration file is further parsed to obtain the configuration information. If no sub-configuration file information is found, a configuration command is sent. This configuration command includes the second path information obtained from the configuration file, specifically... Figure 5 The configuration level client directory and configuration level server directory shown are provided below. The second path information can be used to establish a second download path in subsequent steps. Please refer to the relevant description below for details.

[0097] Step S1611: The server receives the configuration command sent by the client, which is obtained from the configuration file corresponding to the first target directory.

[0098] The client sends the aforementioned configuration command, and the server receives the configuration command. Of course, as mentioned before, this configuration command is obtained by the client parsing the configuration file corresponding to the first target directory.

[0099] In step S1612, the server establishes a second download path for the configuration level server directory and the configuration level client directory based on the second path information in the configuration command, and sends the configuration level server directory to the client through the second download path.

[0100] Upon receiving the configuration command, the server constructs a second download path based on the information in the configuration command. Since the second path information related to the second download path recorded in the configuration text is the configuration level server directory and the configuration level client directory, it is necessary to establish a second download path for the configuration level server directory and the configuration level client directory. Then, the configuration level server directory is sent to the client through the second download path, specifically to the corresponding location of the client's configuration level client directory.

[0101] It should be noted that the configuration level client directory is a directory created under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory. It can be a directory at the same level as the first target directory or a directory at a different level from the first target directory. Otherwise, configuration files are not required, and the files can be downloaded directly through the first download path.

[0102] In one specific implementation, when a first download path between a first target directory and a first client-level directory is established through the client-level directory channel, the step of constructing the second download path may include: setting the configuration level server directory as the second source download address of the client-level directory channel, the address of the configuration level client directory as the second destination download address of the client-level directory channel, and constructing the second download path based on the second source download address and the second destination download address.

[0103] In this way, when establishing the second download path according to the configuration file, it is also done through the client-level directory channel that was created. It is easy to understand that as long as a download path is established between the server and the client-level directory, it is established by the client-level directory channel. In this way, there can be only one client-level directory download channel in the server for the client-level directory, and there is no need to establish a download channel for each subdirectory, thereby saving server resources.

[0104] For ease of understanding, the following example illustrates this: Configuration-level server directories and configuration-level client directories are typically nested modules within an integrated circuit or software, developed by different teams. For example:

[0105] Development team X is responsible for developing functional module X, which nests another smaller functional module Y. Functional module Y is developed by development team Y. On the server, functional module X is directory X, and functional module Y is directory Y. Directory X only includes directories and files other than directory Y (i.e., directory Y is a directory different from directory X). By pointing to directory Y in the configuration file corresponding to directory X, development team X obtains project X (as the first target directory) based on project name X and downloads it to the working directory set on the client (as the client's first-level directory). Then, according to the corresponding configuration file, a second download path is established between directory Y (i.e., the configuration-level server directory) and a nested directory within the working directory (i.e., the configuration-level client directory). This allows directory Y to be sent to the nested directory within the working directory via the second download path.

[0106] It is easy to understand that only after obtaining directory Y can the working directory after obtaining directory X and directory Y become a complete functional module X, which can be developed by development team X.

[0107] Of course, the above example can be expanded according to the actual scenario. As long as the configuration file of the first target directory is specified, the server directories of each configuration level can be downloaded regardless of whether they belong to the first target directory. This ensures that all directories and files belonging to the client's first-level directory can be downloaded smoothly and completely, and multiple address storage is not required.

[0108] It is easy to understand that the directory structure in the server of this application embodiment is that there is only one directory representing each module with the same function (there may be different versions), and the nesting relationship of each directory is realized through configuration files.

[0109] In step S1613, the client receives the configuration level server directory in the configuration command through the second download path and executes step S17.

[0110] The server sends the configuration level server directory. Of course, the client obtains the configuration level server directory from the server through the second download path, thus ending the download of the project directory.

[0111] As can be seen, by setting a configuration file corresponding to the first target directory and specifying the second download paths for the configuration level server directory and configuration level client directory within the configuration file, the configuration level server directory can be retrieved based on this configuration file. This eliminates the need to set related configuration level server directories within the first target directory, allowing the configuration level server directory to be set independently of other related directories without requiring multiple copies. This satisfies the download requirements for the same configuration level server directory across different high-level directories. When developing a new version of the configuration level server directory, only this single directory needs to be developed, and the configuration files in the first target directory (and other related directories) need to be modified to point to the new configuration level server directory, thus enabling development of the project directory and reducing the difficulty of modifying project directories. Furthermore, each directory exists only once on the server, saving storage resources. Maintaining only the configuration file ensures correct file downloads, reducing the maintenance costs of inter-directory relationships and the probability of download errors. Finally, the configuration files can be maintained separately by different developers or teams, transforming centralized directory management into decentralized configuration file management, which is beneficial for collaborative development among teams.

[0112] However, in another specific implementation, as mentioned above, if the client does not need the complete directory, but only the subdirectories or specific files under that directory, then it is not necessary to download all the directories indicated in the configuration file. In this case, sub-configuration file information will be set in the configuration file. Therefore, when the sub-configuration file information of the configuration file is obtained based on the aforementioned step S16, the project directory download method provided in this application embodiment may further include:

[0113] Step S162: The client sends a sub-configuration command obtained from the sub-configuration file corresponding to the sub-configuration file information.

[0114] Once the sub-configuration file information of the configuration file is obtained, the corresponding sub-configuration file is obtained based on the sub-configuration file information, and then the sub-configuration command is sent based on the sub-configuration file.

[0115] As described above regarding configuration files, sub-configuration file information can be the storage address information of the sub-configuration file, thus allowing the corresponding sub-configuration file to be retrieved based on the sub-configuration file information.

[0116] To better understand the structure of the sub-configuration files, please refer to [link / reference]. Figure 6 , Figure 6 This is a schematic diagram of the structure of the sub-configuration file of the project directory download method provided in the embodiments of this application.

[0117] like Figure 6 As shown, the sub-configuration configuration file can include a sub-configuration level server directory and a sub-configuration level client directory, wherein the sub-configuration level server directory indicates where to download the directory from, and the sub-configuration level client directory indicates where to download the directory to.

[0118] Of course, similar to the configuration file, the storage location of the sub-configuration file is also unrestricted, as long as the sub-configuration file information representing the corresponding sub-configuration file is set in the configuration file, and the client can obtain the sub-configuration file based on the sub-configuration file information.

[0119] It is worth noting that in some embodiments, subdirectories can be obtained by directly specifying subdirectories in the configuration file instead of through a subconfiguration file. This application embodiment adds the method of obtaining only subdirectories by setting a subconfiguration file, thereby enabling more flexible acquisition of subdirectories.

[0120] After obtaining the sub-configuration file, the client further parses the sub-configuration file and sends the sub-configuration command to the server based on the parsing result. It is worth noting that the sub-configuration command and the configuration command are two different commands. As can be seen from the description of steps S15 and S16 above, when the client finds no sub-configuration file information after parsing the configuration file, it sends the configuration command according to the configuration file. When it finds sub-configuration file information, it sends the sub-configuration command according to the sub-configuration file.

[0121] Specifically, the configuration commands may include:

[0122] The server directory download source address (equivalent to the configuration level server directory), and the client directory download destination address (equivalent to the configuration level client directory).

[0123] The sub-configuration command may include: the server subdirectory download source address, the client subdirectory download destination address, wherein the server subdirectory download source address is the address of the sub-configuration level server directory, and the client subdirectory download destination address is the address of the sub-configuration level client directory.

[0124] Step S1621: The server receives a sub-configuration command obtained from the sub-configuration file corresponding to the sub-configuration file information of the configuration file.

[0125] In step S1622, the server establishes a third download path for the sub-configuration level server directory and the sub-configuration level client directory based on the third path information in the sub-configuration command, and sends the sub-configuration level server directory to the client through the third download path.

[0126] Upon receiving the sub-configuration instruction, the third download path for the sub-configuration level server directory and the sub-configuration level client directory is constructed based on the third path information in the sub-configuration command. It is easy to understand that the third path information is the sub-configuration level server directory and the sub-configuration level client directory. The sub-configuration level client directory is not necessarily a subdirectory of the configuration level client directory. It is just a different name used to distinguish between the configuration file and the sub-configuration file. However, the sub-configuration level client directory must be a directory under the client's first-level directory, while the sub-configuration level server directory is a directory located in the first target directory.

[0127] Of course, in some embodiments, in order to save on server resources, there is only one client-level directory download channel in the server's client-level directory, and the third and fourth download paths established above are also established by the client-level directory channel.

[0128] It is readily understood that, to facilitate modification and maintenance of the sub-configuration file, the sub-configuration file can be located on a server. Thus, to obtain the sub-configuration file, in one specific embodiment, the sub-configuration file information may include the server storage location and the client-defined storage location of the sub-configuration file. The project directory download method provided in this application embodiment may further include:

[0129] When a sub-configuration file download instruction corresponding to the sub-configuration file information is received, a fourth download path is established between the server storage location and the client's predetermined storage location based on the sub-configuration file download instruction, and the sub-configuration file is sent to the client's predetermined storage location through the fourth download path.

[0130] As can be seen, in the project directory download method provided in this application embodiment, when the client determines that there is sub-configuration file information in the configuration file and the sub-configuration file is stored in the server storage location, it will send a sub-configuration file download instruction. The server will establish a fourth download path and send the sub-configuration file to the client so that the client can perform further parsing and then construct the aforementioned third download path.

[0131] In this way, by storing the sub-configuration files on the server, which can be accessed by multiple clients (development teams), each development team can access the server to modify the configuration files stored on the server after updating the version of the files they are responsible for, so that the configuration files point to the latest version of the files. This makes it convenient to modify and maintain the sub-configuration files. At the same time, the fourth download path built on the system can also ensure that the clients can obtain the sub-configuration files.

[0132] Of course, in other implementations, the sub-configuration files can also be stored directly on the client.

[0133] Step S1623: The client receives the sub-configuration level server directory sent via the third download path.

[0134] Step S17, End.

[0135] End the process of retrieving the project directory.

[0136] It's easy to understand that when no configuration file exists, the client has already downloaded the project directory after obtaining the first target directory, thus ending the process. When the configuration level server directory or sub-configuration level server directory is sent to the client according to the configuration command or sub-configuration command, the client has completed the download process of the project directory on the server, thus ending the process.

[0137] To allow for more flexible version selection, in another specific implementation method, please refer to... Figure 5 As described above, the configuration file may also include version information of each file under the configuration level server directory. Step S13, the step of sending the configuration level server directory to the client through the second download path, includes:

[0138] The directory body of the configuration level server directory and the files corresponding to the version information under the directory body are sent to the client through the second download path.

[0139] It is worth noting that the same file may have different versions. When selecting a file, you must select the specific version of the file. When you do not specify version information in the configuration file, it does not mean that you do not select a version. Instead, the latest version of the specified file (the file in the configuration level server directory) will be selected by default.

[0140] In this way, by setting selectable version information in the configuration file, it is not restricted by file version updates in the configuration level server directory. When a file in the configuration level server directory is updated, the configuration file in the client's first-level directory can choose to update the configuration information in the configuration file, establishing a third download path between the updated configuration level server directory and the configuration level client directory, or it can choose not to update. This allows the update of a certain file to be separated from other projects, and can be pre-updated to the version that other directories will use later, allowing other directories to freely choose the appropriate version. Of course, since a certain functional module in an integrated circuit or software needs to maintain version consistency, when the configuration level server directory specified in the configuration file is a specific version, if the configuration files in other directories of the integrated circuit or software specify the same configuration level server directory, then all of them must specify the same specific version of the configuration level server directory.

[0141] To further conserve server resources, in one specific embodiment, the configuration level server directory includes a common directory, such as... Figure 4 The "Common" directory shown.

[0142] It is easy to understand that the common directory contains the parts that are common to all directories. The degree of commonality can be freely chosen according to the specific scenario. It can be considered that only modules or files that need to be nested in all directories are considered common, or it can be considered that as long as more than one directory has the same directory or file, it can be put into the common directory. Of course, usually the standard between the two is used to determine the files or subdirectories that need to be put into the common directory.

[0143] In this way, duplicate directories or files contained in various directories on the server can be kept in their entirety. By simply setting a configuration file to specify the common directory or further using a sub-configuration file to specify certain subdirectories or files within the common directory, the download from that directory to the client's first-level directory can be achieved, further reducing the server resource usage.

[0144] When the server receives a new version file and needs to specify the new version file through a configuration file, it is easy to understand that the configuration file needs to be updated. In one specific embodiment, the project directory download method provided in this application may further include:

[0145] When a configuration file update command is received, the configuration file in the first target directory is updated according to the configuration file update command.

[0146] After receiving the update command, the server modifies the file version specification in the configuration file so that the client can obtain the new version file based on the updated configuration file. It is easy to understand that, in order to give developers the right to choose the file version, in some embodiments, the issuer of the configuration command and sub-configuration command can update the version information recorded in the configuration file.

[0147] Of course, sub-configuration files can also be updated; please refer to the above description of configuration file updates for details.

[0148] To improve the accuracy of project directory downloads, prevent human error, and increase the efficiency of project directory downloads, in one specific embodiment, the directory download method can be implemented using a script.

[0149] Specifically, after the client creates a client-level directory, a script is imported into the client-level directory. The script takes a directory name as input, parses the directory name, and automatically downloads the server-level directory of the first target directory to the client-level directory of the client-level directory according to the pre-set first download path. The script then creates client-level directories at each level under the client-level directory. After that, the script automatically checks if there is a configuration file and reads the configuration file. Based on the configuration file, it automatically generates configuration commands, thereby automating the entire directory download process.

[0150] In this way, directory downloads can be performed quickly using scripts, improving the efficiency of directory downloads. Furthermore, only the script needs to be maintained to ensure that each download is error-free, thus improving both efficiency and accuracy.

[0151] In one specific embodiment, download information for the project directory is recorded, including the download directory path, file version information, and download logs.

[0152] When downloading automatically via scripts, all intermediate processes are handled by the scripts, which is not conducive to human understanding. Therefore, to improve human understanding and later maintenance, download information in the project directory can be recorded, including the download directory path, the version information of the downloaded files, and all download logs.

[0153] The following describes the project directory download device provided in the embodiments of this disclosure. The test point verification device described below can be considered as the functional module architecture required for an electronic device (such as a PC) to implement the project directory download method provided in the embodiments of this disclosure. The content of the project directory download device described below can be referred to in correspondence with the content of the project directory download method described above.

[0154] This application also provides a project catalog download device, please refer to... Figure 7 , Figure 7 This is a block diagram of a project catalog download device provided in an embodiment of this application.

[0155] like Figure 7 As shown, the project directory download device provided in this application embodiment is suitable for a server and includes:

[0156] The directory name acquisition unit 11 is adapted to acquire a first target directory based on the directory name, wherein the first target directory includes server-level directories corresponding to the directory name in the server.

[0157] The first target directory sending unit 12 is adapted to send the first target directory to the client through the first download path according to the first download path between the server-level directory of the first target directory and the pre-established client-level directory, so that the client can establish corresponding client-level directories under the client-level directory.

[0158] The configuration level server directory sending unit 13 is adapted to, when receiving a configuration command sent by a client based on a configuration file corresponding to the first target directory, establish a second download path for the configuration level server directory and the configuration level client directory based on the second path information in the configuration command, and send the configuration level server directory to the client through the second download path, wherein the configuration level client directory is a directory established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory.

[0159] As can be seen, by setting a configuration file corresponding to the first target directory and specifying the second download paths for the configuration level server directory and configuration level client directory within the configuration file, the configuration level server directory can be retrieved based on this configuration file. This eliminates the need to set related configuration level server directories within the first target directory, allowing the configuration level server directory to be set independently of other related directories without requiring multiple copies. This satisfies the download requirements for the same configuration level server directory across different high-level directories. When developing a new version of the configuration level server directory, only this single directory needs to be developed, and the configuration files in the first target directory (and other related directories) need to be modified to point to the new configuration level server directory, thus enabling development of the project directory and reducing the difficulty of modifying project directories. Furthermore, each directory exists only once on the server, saving storage resources. Maintaining only the configuration file ensures correct file downloads, reducing the maintenance costs of inter-directory relationships and the probability of download errors. Finally, the configuration files can be maintained separately by different developers or teams, transforming centralized directory management into decentralized configuration file management, which is beneficial for collaborative development among teams.

[0160] In some embodiments, the first target directory includes the configuration file, and the first target directory sending unit is adapted to send the first target directory to the client via its corresponding first download path, including:

[0161] The configuration file in the first target directory is sent to the client via the first download path.

[0162] In some embodiments, it also includes:

[0163] The sub-configuration level server directory sending unit 14 is adapted to, when receiving a sub-configuration command sent by a client, which is obtained from the sub-configuration file corresponding to the sub-configuration file information of the configuration file, establish a third download path for the sub-configuration level server directory and the sub-configuration level client directory according to the third path information in the sub-configuration command, and send the sub-configuration level server directory to the client through the third download path, wherein the sub-configuration level server directory is a sub-directory of the configuration level server directory.

[0164] In some embodiments, the sub-configuration file information includes the server storage location and the client-predetermined storage location of the sub-configuration file, and the apparatus further includes:

[0165] The sub-configuration file sending unit 15 is adapted to establish the server storage location and the client predetermined storage location of the sub-configuration file according to the sub-configuration file download instruction when it receives a sub-configuration file download instruction corresponding to the sub-configuration file information.

[0166] In some embodiments, the configuration file further includes version information of each file under the level server directory, and the configuration level server directory sending unit is adapted to send the configuration level server directory to the client through the second download path, including:

[0167] It is suitable to send the directory body of the configuration level server directory and the files corresponding to the version information under the directory body to the client through the second download path.

[0168] In some embodiments, the configuration level server directory includes a common directory.

[0169] In some embodiments, the first download path is constructed by a first download path construction unit. This first download path construction unit is adapted to receive a client-level directory channel creation command, create a client-level directory channel corresponding to the client-level directory, set the server-level directory as the first source download address of the client-level directory channel, and the client-level directory as the first destination download address of the client-level directory channel. The first download path is then constructed based on the first source download path and the first destination download address. The configuration level server directory is set as the second source download address of the client-level directory channel, and the address of the configuration level client directory is set as the second destination download address of the client-level directory channel. The second download path is then constructed based on the second source download address and the second destination download address.

[0170] In some embodiments, the project directory downloading device utilizes a script to download the project directory.

[0171] In some embodiments, it also includes:

[0172] Server download information recording unit 16 is adapted to record download information of the project directory, the download information including the first download path, the second download path, file version information and download log.

[0173] In some embodiments, it also includes:

[0174] Server configuration file update unit 17 is adapted to update the configuration file according to the configuration file update command when a configuration file update command is received.

[0175] This application also provides a project catalog download device, please refer to... Figure 8 , Figure 8 Another block diagram of the project catalog download device provided in the embodiments of this application.

[0176] like Figure 8 As shown, the project catalog download device provided in this application embodiment is applicable to a client and includes:

[0177] The directory name sending unit 21 is adapted to create a client-level directory and send the directory name of the client-level directory so that the server can obtain a first target directory corresponding to the directory name. The first target directory includes server-level directories corresponding to the directory name.

[0178] The first target directory receiving unit 22 is adapted to receive the first target directory sent through the first download path between the server-level directory and the client-level directory of the first target directory, and to establish corresponding client-level directories under the client-level directory;

[0179] The configuration command sending unit 23 is adapted to send a configuration command when no sub-configuration file information is obtained after parsing the configuration file corresponding to the first target directory, and to receive the configuration level server directory in the configuration command through the second download path. The second download path is the path between the configuration level server directory and the configuration level client directory established according to the second path information in the configuration command. The configuration level client directory is the client's various levels of directories established under the client's first-level directory. The configuration level server directory is a directory different from the first target directory.

[0180] In some embodiments, it also includes:

[0181] The sub-configuration command sending unit 24 is adapted to send a sub-configuration command obtained from the sub-configuration file corresponding to the sub-configuration file information when parsing the configuration file to obtain the sub-configuration file information;

[0182] The sub-configuration level server directory receiving unit 25 is adapted to receive the sub-configuration level server directory sent through a third download path, wherein the third download path is the path between the sub-configuration level server directory and the sub-configuration level client directory established according to the third path information in the sub-configuration information of the sub-configuration command.

[0183] In some embodiments, the sub-configuration file information includes the server storage location and the client-predetermined storage location of the sub-configuration file, and the project directory download device further includes:

[0184] Sub-configuration file download instruction sending unit 26 is adapted to send a sub-configuration file download instruction corresponding to the sub-configuration file information;

[0185] The sub-configuration file receiving unit 27 is adapted to receive the sub-configuration file sent to the client's predetermined storage location via a fourth download path, wherein the fourth download path is a path between the server storage location and the client's predetermined storage location established according to the sub-configuration file download instruction.

[0186] In some embodiments, the configuration file further includes version information of each file under the level server directory, and the configuration command sending unit is adapted to receive the configuration level server directory in the configuration command through the second download path, including:

[0187] The system receives the directory body of the configuration level server directory and the files corresponding to the version information under the directory body through the second download path.

[0188] In some embodiments, the directory downloading device utilizes a script to download the project directory.

[0189] In some embodiments, it also includes:

[0190] The client download information recording unit 28 is suitable for recording download information of the project directory, including download directory path, file version information and download log.

[0191] In some embodiments, it also includes:

[0192] The client configuration file update unit 29 is adapted to send a configuration file update command so that the server updates the configuration file according to the configuration file update command.

[0193] This application embodiment also provides a server that stores a project directory download program to implement the project directory download method applicable to the server as described above.

[0194] This application also provides a client application that stores a project directory download program to implement the project directory download method applicable to the client described above.

[0195] This application also provides a storage medium storing a project directory download program to implement the project directory download method described in any of the above claims.

[0196] As can be seen, by setting a configuration file corresponding to the first target directory and specifying the second download paths for the configuration level server directory and configuration level client directory within the configuration file, the configuration level server directory can be retrieved based on this configuration file. This eliminates the need to set related configuration level server directories within the first target directory, allowing the configuration level server directory to be set independently of other related directories without requiring multiple copies. This satisfies the download requirements for the same configuration level server directory across different high-level directories. When developing a new version of the configuration level server directory, only this single directory needs to be developed, and the configuration files in the first target directory (and other related directories) need to be modified to point to the new configuration level server directory, thus enabling development of the project directory and reducing the difficulty of modifying project directories. Furthermore, each directory exists only once on the server, saving storage resources. Maintaining only the configuration file ensures correct file downloads, reducing the maintenance costs of inter-directory relationships and the probability of download errors. Finally, the configuration files can be maintained separately by different developers or teams, transforming centralized directory management into decentralized configuration file management, which is beneficial for collaborative development among teams.

[0197] The foregoing describes multiple embodiment schemes provided by the embodiments of this application. The optional methods described in each embodiment scheme can be combined and cross-referenced with each other without conflict, thereby extending to a variety of possible embodiment schemes. These can all be considered as the embodiment schemes disclosed and published by the embodiments of this application.

[0198] While the embodiments disclosed above are described in this application, this application is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of this application; therefore, the scope of protection of this application should be determined by the scope defined in the claims.

Claims

1. A method for downloading a project directory, characterized in that, Applicable to servers, including: Obtain a directory name, and obtain a first target directory based on the directory name. The first target directory includes various levels of directories on the server that correspond to the directory name. The first target directory includes configuration files. Based on the first download path between the server-level directory of the first target directory and the pre-established client-level directory, the first target directory is sent to the client through the first download path, so that the client can establish corresponding client-level directories under the client-level directory; When a configuration command is received from the client based on the configuration file corresponding to the first target directory, a second download path is established for the configuration level server directory and the configuration level client directory according to the second path information in the configuration command. The configuration level server directory is then sent to the client through the second download path. The configuration level client directory is a directory established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory. The configuration file also includes version information for each file in the configuration level server directory. The step of sending the configuration level server directory to the client via the second download path includes: The directory body of the configuration level server directory and the files corresponding to the version information under the directory body are sent to the client through the second download path.

2. The project directory download method as described in claim 1, characterized in that, Sending the first target directory to the client via the first download path includes: The configuration file in the first target directory is sent to the client via the first download path.

3. The project directory download method as described in claim 1, characterized in that, Also includes: When a sub-configuration command is received from the client, which is obtained from the sub-configuration file corresponding to the sub-configuration file information of the configuration file, a third download path is established for the sub-configuration level server directory and the sub-configuration level client directory based on the third path information in the sub-configuration command. The sub-configuration level server directory is then sent to the client through the third download path. The sub-configuration level server directory is a subdirectory of the configuration level server directory, and the sub-configuration level client directory is a directory under the configuration level client directory.

4. The project directory download method as described in claim 3, characterized in that, The sub-configuration file information includes the server storage location and the client-defined storage location of the sub-configuration file. The method further includes: When a sub-configuration file download instruction corresponding to the sub-configuration file information is received, a fourth download path is established between the server storage location and the client's predetermined storage location based on the sub-configuration file download instruction, and the sub-configuration file is sent to the client's predetermined storage location through the fourth download path.

5. The project directory download method as described in claim 1, characterized in that, The configuration level server directory includes a common directory.

6. The project directory download method as described in claim 1, characterized in that, The steps for constructing the first download path include: Receive a client-side first-level directory channel creation command and create a client-side first-level directory channel corresponding to the client-side first-level directory; The server's first-level directory is set as the first source download address of the client's first-level directory channel, and the client's first-level directory is set as the first destination download address of the client's first-level directory channel. The first download path is constructed based on the first source download address and the first destination download address. The steps for constructing the second download path include: The configuration level server directory is set as the second source download address of the client's first-level directory channel, and the address of the configuration level client directory is set as the second destination download address of the client's first-level directory channel. The second download path is constructed based on the second source download address and the second destination download address.

7. The project directory download method as described in any one of claims 1-6, characterized in that, The directory download method is implemented using a script.

8. The project directory download method as described in claim 7, characterized in that, Also includes: The download information of the project directory is recorded, including the first download path, the second download path, file version information, and download logs.

9. The project directory download method as described in any one of claims 2-6, characterized in that, Also includes: When a configuration file update command is received, the configuration file is updated according to the configuration file update command.

10. A method for downloading a project directory, characterized in that, For clients, including: Create a client-side first-level directory and send the directory name of the client-side first-level directory so that the server can obtain the first target directory corresponding to the directory name. The first target directory includes all levels of server directories corresponding to the directory name. Receive the first target directory sent through the first download path between the server-level directory and the client-level directory, and create corresponding client-level directories under the client-level directory; When parsing the configuration file corresponding to the first target directory and no sub-configuration file information is obtained, a configuration command is sent, and the configuration level server directory in the configuration command is received through the second download path. The sub-configuration file information corresponds to a sub-configuration file, which includes a sub-configuration level server directory and a sub-configuration level client directory. The second download path is the path between the configuration level server directory and the configuration level client directory established based on the second path information in the configuration command. The configuration level client directory is the client's various levels of directories established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory. The configuration file also includes version information for each file in the level server directory. The step of receiving the configuration level server directory in the configuration command through the second download path includes: The system receives the directory body of the configuration level server directory and the files corresponding to the version information under the directory body through the second download path.

11. The project directory download method as described in claim 10, characterized in that, Also includes: When the configuration file is parsed to obtain the sub-configuration file information, a sub-configuration command obtained from the sub-configuration file corresponding to the sub-configuration file information is sent. The system receives a sub-configuration level server directory sent via a third download path. The third download path is a path between the sub-configuration level server directory and the sub-configuration level client directory established based on the third path information in the sub-configuration information of the sub-configuration command. The sub-configuration level server directory is a subdirectory of the configuration level server directory, and the sub-configuration level client directory is a directory under the configuration level client directory.

12. The project directory download method as described in claim 11, characterized in that, The sub-configuration file information includes the server storage location and the client-defined storage location of the sub-configuration file. The method further includes: Send a sub-configuration file download command corresponding to the sub-configuration file information; The client receives the sub-configuration file sent to a predetermined storage location via a fourth download path, wherein the fourth download path is a path between the server storage location and the client predetermined storage location established according to the sub-configuration file download instruction.

13. The project directory download method as described in claim 10, characterized in that, The configuration file also includes version information for each file in the level server directory. The step of receiving the configuration level server directory in the configuration command via the second download path includes: The system receives the directory body of the configuration level server directory and the files corresponding to the version information under the directory body through the second download path.

14. The project directory download method as described in any one of claims 10-13, characterized in that, The directory download method is implemented using a script.

15. The project directory download method as described in claim 14, characterized in that, Also includes: Record download information for the project directory, including the download directory path, file version information, and download logs.

16. The project directory download method as described in any one of claims 10-13, characterized in that, Also includes: Send a configuration file update command so that the server updates the configuration file according to the configuration file update command.

17. A project catalog download device, characterized in that, Applicable to servers, including: The directory name acquisition unit is adapted to acquire a first target directory based on the directory name, wherein the first target directory includes server-level directories corresponding to the directory name in the server; and the first target directory includes configuration files. The first target directory sending unit is adapted to send the first target directory to the client through the first download path according to the first download path between the server-level directory of the first target directory and the pre-established client-level directory, so that the client can establish corresponding client-level directories under the client-level directory; The configuration level server directory sending unit is adapted to, when receiving a configuration command sent by a client based on a configuration file corresponding to the first target directory, establish a second download path for the configuration level server directory and the configuration level client directory based on the second path information in the configuration command, and send the configuration level server directory to the client through the second download path, wherein the configuration level client directory is a directory established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory; The configuration file also includes version information for each file in the configuration level server directory. The configuration level server directory sending unit sends the configuration level server directory to the client via the second download path, including: The directory body of the configuration level server directory and the files corresponding to the version information under the directory body are sent to the client through the second download path.

18. The project catalog download device as described in claim 17, characterized in that, The first target directory includes the configuration file. The first target directory sending unit, adapted to send the first target directory to the client via the first download path, includes: The configuration file in the first target directory is sent to the client via the first download path.

19. The project catalog download device as described in claim 17, characterized in that, Also includes: The sub-configuration level server directory sending unit is adapted to, when receiving a sub-configuration command sent by a client, which is obtained from a sub-configuration file corresponding to the sub-configuration file information of the configuration file, establish a third download path for the sub-configuration level server directory and the sub-configuration level client directory based on the third path information in the sub-configuration command, and send the sub-configuration level server directory to the client through the third download path, wherein the sub-configuration level server directory is a subdirectory of the configuration level server directory; and the sub-configuration level client directory is a directory under the configuration level client directory.

20. The project catalog download device as described in claim 19, characterized in that, The sub-configuration file information includes the server storage location and the client-defined storage location of the sub-configuration file. The device further includes: The sub-configuration file sending unit is adapted to, when receiving a sub-configuration file download instruction corresponding to the sub-configuration file information, establish the server storage location and the client predetermined storage location of the sub-configuration file according to the sub-configuration file download instruction.

21. The project catalog download device as described in claim 17, characterized in that, The configuration file also includes version information for each file in the level server directory. The configuration level server directory sending unit is adapted to send the configuration level server directory to the client via the second download path, including: It is suitable to send the directory body of the configuration level server directory and the files corresponding to the version information under the directory body to the client through the second download path.

22. The project catalog download device as described in claim 17, characterized in that, The first download path is constructed by a first download path construction unit. The first download path construction unit is adapted to receive a client first-level directory channel creation command, create a client first-level directory channel corresponding to the client first-level directory, set the server first-level directory as the first source download address of the client first-level directory channel, set the client first-level directory as the first destination download address of the client first-level directory channel, and construct the first download path according to the first source download path and the first destination download address. The configuration level server directory is set as the second source download address of the client's first-level directory channel, and the address of the configuration level client directory is set as the second destination download address of the client's first-level directory channel. The second download path is constructed based on the second source download address and the second destination download address.

23. The project catalog download device according to any one of claims 17-22, characterized in that, The project directory download device uses a script to download the project directory.

24. The project catalog download device as described in claim 23, characterized in that, Also includes: The server download information recording unit is adapted to record download information of the project directory, including the first download path, the second download path, file version information, and download logs.

25. A project catalog download device, characterized in that, For clients, including: The directory name sending unit is adapted to create a client-level directory and send the directory name of the client-level directory so that the server can obtain a first target directory corresponding to the directory name. The first target directory includes server-level directories corresponding to the directory name. The first target directory receiving unit is adapted to receive the first target directory sent through the first download path between the server-level directory and the client-level directory of the first target directory, and to establish corresponding client-level directories under the client-level directory; The configuration command sending unit is adapted to send a configuration command when, after parsing the configuration file corresponding to the first target directory, no sub-configuration file information is obtained, and to receive the configuration level server directory in the configuration command through a second download path. The sub-configuration file information corresponds to a sub-configuration file, which includes a sub-configuration level server directory and a sub-configuration level client directory. The second download path is a path between the configuration level server directory and the configuration level client directory established based on the second path information in the configuration command. The configuration level client directory is the client's various levels of directories established under the client's first-level directory, and the configuration level server directory is a directory different from the first target directory. The configuration file also includes version information for each file in the level server directory. The configuration command sending unit receives the configuration level server directory in the configuration command through the second download path, including: The system receives the directory body of the configuration level server directory and the files corresponding to the version information under the directory body through the second download path.

26. The project catalog download device as described in claim 25, characterized in that, Also includes: The sub-configuration command sending unit is adapted to send a sub-configuration command obtained from the sub-configuration file corresponding to the sub-configuration file information when the sub-configuration file information is obtained by parsing the configuration file; The sub-configuration level server directory receiving unit is adapted to receive a sub-configuration level server directory sent via a third download path. The third download path is a path between the sub-configuration level server directory and the sub-configuration level client directory established according to the third path information in the sub-configuration information of the sub-configuration command. The sub-configuration level server directory is a subdirectory of the configuration level server directory, and the sub-configuration level client directory is a directory under the configuration level client directory.

27. The project catalog download device as described in claim 26, characterized in that, The sub-configuration file information includes the server storage location and the client-defined storage location of the sub-configuration file. The project directory download device further includes: Sub-configuration file download instruction sending unit, adapted to send a sub-configuration file download instruction corresponding to the sub-configuration file information; The sub-configuration file receiving unit is adapted to receive the sub-configuration file sent to the client's predetermined storage location via a fourth download path, wherein the fourth download path is a path between the server's storage location and the client's predetermined storage location established according to the sub-configuration file download instruction.

28. The project catalog download device as described in claim 25, characterized in that, The configuration file also includes version information for each file in the level server directory. The configuration command sending unit is adapted to receive the configuration level server directory in the configuration command through the second download path, including: The system receives the directory body of the configuration level server directory and the files corresponding to the version information under the directory body through the second download path.

29. The project catalog download device according to any one of claims 25-28, characterized in that, The directory download device uses a script to download the project directory.

30. The project catalog download device as described in claim 29, characterized in that, Also includes: The client download information recording unit is suitable for recording download information of the project directory, including download directory path, file version information, and download logs.

31. A server, characterized in that, The server stores a project directory download program to implement the project directory download method as described in any one of claims 1-9.

32. A client application, characterized in that, The client stores a project directory download program to implement the project directory download method as described in any one of claims 10-16.

33. A storage medium, characterized in that, The storage medium stores a project directory download program to implement the project directory download method as described in any one of claims 1-16.

Images