CN102024005B - Issuance system and method of information item set directories - Google Patents

Abstract

The invention discloses a publishing system and method of an information item collection directory, which enables the synchronization of the information item collection directories of the server and the client. The technical solution is: the client interacts with the directory release server through a communication channel, downloads the release directory on the server to the local client to create a local copy, and keeps in sync with the update status of the release directory. In addition, the client uploads the modification operation of the published directory to the directory publishing server, updates the published directory stored in the directory database storage module in sequence after sorting, and records the successful update operation with an update stamp in the update log database storage module middle.

Description

System and method for publishing information item collection catalog

technical field

The present invention relates to a computer system, in particular to a system and method for publishing an information item collection directory.

Background technique

RSS (Simple Information Synthesis) is a website information publishing technology that is widely used on the Internet now. It allows users to aggregate information items from multiple information publishing sources selected into a unified regular tree directory as a search entry, allowing users to pass This unified retrieval portal retrieves information from different information publishing sites.

Since RSS uses a conventional tree directory, RSS has a series of problems caused by the conventional tree directory structure:

(1) A project can only belong to one directory;

(2) fixed retrieval path;

(3) The combination of classification modes causes path branch explosion;

(4) Items cannot be retrieved based on item-specific attribute values

The applicant proposed relevant information items in the patent application filed on July 20, 2007, with a publication date of April 9, 2008, publication number CN101158949, and the title of the invention "Method and System for Classification and Retrieval of Document Items Based on Sets" The technical scheme of collection directory is used to solve the above four problems. The applicant submitted a patent application with the application number PCT/CN2009/072520 and the title of the invention "Aggregation Method and System for Information Item Collection Catalog" on June 30, 2009. In this patent application, the logic of aggregating information item collection catalogs was proposed. The scheme, but did not propose how to publish the catalog of information items through the network, which makes the scheme unrealizable.

Contents of the invention

The purpose of the present invention is to solve the above problems, and provides a publishing system of an information item collection directory, which enables the synchronization of the information item collection directory of the server and the client, and enhances the feasibility of related schemes for the information item collection directory.

Another object of the present invention is to provide a publishing method for an information item collection directory.

The technical solution of the present invention is: the present invention discloses a publishing system for an information item collection directory, including:

Directory Publisher, further comprising:

The directory database storage module is used to store: the published information item collection directory and the update stamp corresponding to the directory;

The update log database storage module is used to stamp an update stamp on each successful update operation of the released information item collection directory, and store it as an update record;

Upload the update component, connect the directory database storage module and the update log database storage module and the directory database compressed snapshot storage module, update the update operation of the client to the published information item collection directory to the directory database storage module and record the successful update operation The information is saved to the update log database storage module, and when the current cumulative number of successful update operations exceeds the preset threshold value, a compressed snapshot is generated with the current content of the directory database storage module and saved to the directory database compressed snapshot storage module;

The directory database compressed snapshot storage module is connected to the upload update component and the download update component, and is used to store the compressed snapshot of the content in the directory database storage module;

Download the update component, connect the update log database storage module and the directory database compressed snapshot storage module, use the update record in the update log database storage module and the compressed snapshot in the directory database compressed snapshot storage module, and cooperate with the client to update the published information of the client A copy of the project collection directory;

The server-side communication component is used to establish a communication connection with the client and perform the task of sending and receiving data with the client;

The client, interacting with the directory publishing server via a communication channel, further includes:

The local directory storage module is used to store on the client side including: a copy of the published information item collection directory and an update stamp corresponding to the copy;

The snapshot downloads and updates the synchronization component, connects to the local directory storage module, and updates the copy of the published information item collection directory of the client using the update log of the directory publishing server or the compressed snapshot of the directory publishing server;

The update task generation and submission component generates update tasks according to user operations and submits them to the directory publishing server;

The client communication component establishes a communication connection with the directory publishing server and fulfills the task of sending and receiving data with the server.

According to an embodiment of the publishing system of the information item collection directory of the present invention, the directory database storage module further includes:

The information item collection storage unit records the identification of each information item collection in the information item collection directory, the parent-child relationship between the information item collection and other information item collections in the information item collection directory, the attribute specification of the information item collection and other information Ancillary information for the set of information items;

The information item storage unit, for each information item in the information item collection directory, records its identification, the information item set to which the information item belongs, the attributes owned by the information item and the corresponding attribute values, and other auxiliary information of the information item;

The update stamp unit records the update stamp of the information item collection catalog stored by the catalog database storage module.

According to an embodiment of the publishing system of the information item collection directory of the present invention, multiple records recording the following information are stored in the update log database storage module: update stamp, object type, identification, operation type, and operation parameter.

According to an embodiment of the publishing system of the information item collection directory of the present invention, the publishing system further includes:

The retrieval component is connected to the local directory storage module, and is used for retrieval operation in the information item collection directory of the client.

According to an embodiment of the publishing system of the information item collection directory of the present invention, the publishing system further includes:

The directory aggregation component is connected to the local directory storage module, and is used for performing aggregation operations on the information item collection directory in the client.

The present invention also discloses a publishing method of an information item collection directory. The publishing method includes the process of uploading and updating operations by the client and the process of downloading and publishing the directory by the server to update the local copy of the directory.

The process of client upload update operation further includes:

Generate an update task according to the user interface operation of the client;

Submit the update task to the server;

According to the received update task, the server updates the publishing directory corresponding to the task on the server in sequence according to the multiple update operation information contained in the task, and increases the update stamp of the directory by one unit when each update is successful, and updates this time The update operation information is marked with the update stamp of the catalog and saved to the update log to form an update record. The update log is associated with the server release directory through the update stamp;

If the current accumulative number of successful update operations corresponding to the directory exceeds the preset threshold, the publishing directory will be compressed as a whole to generate a compressed snapshot, and the count will be cleared;

The process for the client to download the server's published catalog to update the local catalog copy further includes:

The client requests to query the current update status of the catalog published by the server, including the current update stamp of the catalog published by the server and the update stamp range of the update log;

After comparing the update stamp range of the server-published directory and the update stamp range of the update log with the update stamp of the client's local directory copy, choose one of the two methods of downloading update logs and downloading compressed snapshots to update the local directory copy.

According to an embodiment of the publishing method of the information item collection directory of the present invention, the update record in the update log includes: update stamp, object type, identification, operation type, and operation parameter.

According to an embodiment of the publishing method of the information item collection directory of the present invention, after comparing the update stamp range of the directory update log issued by the server and the update stamp range of the directory update log with the update stamp of the client's local directory copy, download and update the local directory copy. The step further includes performing directory update in three cases:

If the update stamp of the local directory copy is equal to the update stamp of the server-published directory, wait for a preset period of time before comparing the update stamps;

If the update stamp of the local directory copy is older than the update stamp of the server published directory and the required update operation is within the update stamp range of the changelog, download the required changelog and update the local directory in the order of the update stamp of the changelog copy;

If the update stamp of the local directory copy is older than the update stamp of the server published directory and the required update operation is not within the update stamp range of the changelog, download the compressed snapshot and decompress to rebuild the local directory copy.

Compared with the prior art, the present invention has the following beneficial effects: the technical solution of the present invention is that the client interacts with the catalog publishing server through the communication channel, downloads the publishing catalog on the server to the local client to create a local copy, and updates the status with the publishing catalog keep in sync. In addition, the client uploads the modification operation of the published directory to the directory publishing server, updates the published directory stored in the directory database storage module in sequence after sorting, and records the successful update operation with an update stamp in the update log database storage module middle.

Description of drawings

Fig. 1 is a schematic diagram of the structure of an embodiment of the publishing system of the information item collection directory of the present invention.

Fig. 2 is a schematic structural diagram of the directory publishing server of the present invention.

Fig. 3 is a schematic structural diagram of the client of the present invention.

Fig. 4 is a schematic diagram of the directory database storage module of the present invention.

Fig. 5 is a schematic diagram of an update log database storage module of the present invention.

Fig. 6 is a schematic diagram of uploading and updating operations of the client in the present invention.

Fig. 7 is a schematic diagram of the client downloading the server to publish the directory to update the local directory copy in the present invention.

Detailed ways

The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

Before introducing the embodiments of the present invention, it is necessary to explain the technical terms and technical background involved in the present invention.

The information item collection directory is the object to be processed by the publishing system of the present invention. An information item is defined as an information structure that can be processed on a computer system and presented to a user as a logical whole. A file in a file system is a typical example of an information item, but not only a file is an information item. For example, a record in a relational database is physically stored as a part of the database file, but logically it can be processed and displayed to the user as a whole, so a record in a relational database can also be an example of an information item. For another example, an email in mail sending and receiving software such as Outlook is also stored as a part in the mailbox file, but logically it can also be processed and displayed as a whole, so email can also be an example of an information item.

The information item set is a mathematical set composed of n information items, where n is an integer greater than or equal to 0. In practical applications, an information item set may contain multiple information items.

The information item set directory is an information structure composed of n information item sets through a parent-child relationship, where n is an integer greater than or equal to 0. The concept of the parent set is limited to: if the specified information item set A is the parent set of the information item set B, then all the information items included in B are also included in A, and B can be said to be a sub-set of A.

In actual processing, information items are often uniquely represented by an identifier. For example, a file in an operating system is represented by a unique file path, and a web page on the Internet can be represented by a unique URL. As long as appropriate grammar rules are designed, any type of information item can be uniquely identified by a text string. Therefore, in practical applications, the information item collection stores the identifier representing the information item ontology rather than the information itself contained in the information item. Therefore, an information item collection can contain various information items, and an information item collection directory can be used to manage various types of information items from multiple information sources. For example: an information item collection directory is set on a personal computer to manage various local files and e-mails, and this directory can also be used to manage various information items including web pages from different websites on the Internet.

Publishing system for catalog of information item collections

Referring to FIG. 1 below, FIG. 1 shows the basic architecture of the publishing system of the information item collection directory. The publishing system consists of two parts: the directory publishing server and the client. On the one hand, the client interacts with the directory publishing server through the communication channel, downloads the publishing directory on the directory publishing server to the client, creates a local copy, and keeps updating and synchronizing with the publishing directory. On the other hand, the client uploads the modification operation of the publishing directory to the directory publishing server, enters the update task queue, updates the published directory in order, and records the successful updating operation with an update stamp in the update log database.

Fig. 2 shows the structure of the directory distribution server. The directory publishing server includes the following modules: directory database storage module 10 , update log database storage module 11 , directory database compressed snapshot storage module 12 , upload update component 13 , download update component 14 and server-side communication component 15 . The connection relationship between these modules is: the server-side communication component 15 connects the upload update component 13 and the download update component 14 . The upload update component 13 is respectively connected to the directory database storage module 10 , the update log database storage module 11 , and the directory database compressed snapshot storage module 12 . The download and update component 14 is respectively connected to the update log database storage module 11 and the directory database compressed snapshot storage module 12 .

A directory publishing server can manage the updating and publishing of multiple directories at the same time. An independent set of data storage consisting of a directory database storage module 10 , an update log database storage module 11 and a directory database compressed snapshot storage module 12 is required for a single directory. Unless otherwise specified, the follow-up content of this case is aimed at publishing a catalog. The directory database storage module 10 is used to store the published information item collection directory and other information closely related to the directory itself required for publishing, such as update stamps corresponding to the directory. From the perspective of actual processing, there are two kinds of objects in an information item collection directory, one is the information item collection, and the information to be recorded includes: the identification of the information item collection, the information item collection and other information item collections in the directory The parent-child relationship between the information item set, the attribute specification of the information item set, and other auxiliary information of the information item set; the other is the information item, and the information that needs to be recorded includes: the identification of the information item, and the information item is in the information item set directory The set of information items to which the information item belongs, the attributes and corresponding attribute values of the information item, and other auxiliary information of the information item. FIG. 4 shows the logical configuration of the directory database storage module 10 . According to the above analysis, the directory database storage module 10 logically includes at least two blocks, one for recording the relevant information of each information item set in the directory is called the information item set storage unit 100, and one for recording each information item set in the directory Information about an information item is referred to as an information item storage unit 102 . Of course, this division does not represent the data structure in the directory database in actual implementation, but only represents the logical composition of the data components of the directory database storage module. In addition, considering the need to record the update status of the publishing catalog, the catalog database storage module 10 of the present invention also adds an update stamp unit 104 for recording update stamp information. The update stamp is used to characterize the sequence state in which the directory is updated. In the implementation, the update stamp can be a natural number variable. When a successful update operation is performed on the directory stored in the directory database storage module 10, the update stamp will increase by one immediately, and then the The update stamp used to record the information of this update operation in the update log database module 11 must be completely consistent with the update stamp of the directory when this operation is completed.

The updating operation for the directory can be divided into updating the information item set and updating the information item according to different objects. The update operation of the information item collection can be further divided into: adding an information item collection; deleting an information item collection; modifying the identification of an existing information item collection in the directory, the parent-child relationship between it and other information item collections in the directory, Its attribute specification and other ancillary information. The update operations for information items include: adding an information item to the directory (that is, setting the affiliation relationship between the information item and the information item collection in the directory); deleting an item from the directory (that is, removing the item and any information item in the directory). Affiliation relationship between collections); modify the identity of an information item in the directory, its affiliation relationship with the information item collection in the directory, its attribute values and other auxiliary information. According to the common points of update operations, whether an update operation is aimed at an information item set or an information item, no matter what content is updated, it can be used to include: the type of the update object, the identity of the update object, the type of the update operation, and the update operation. It needs to be represented by a record of several parameters and other fields. FIG. 5 shows the data structure of the update log database storage module 11 . For example, the first update record stored in the update log database storage module 11 of Fig. 5 is: the update stamp is 101, the update object type is an information item collection, and the update object is identified as "archive" (in actual processing, one is often used to match the information The connotation of the item set is consistent and the unique name within the scope of the information item set directory is used as the identification of the information item set, which is the processing method used here), the operation type is modification, and the value of each operation parameter. Only successfully executed update operations will be recorded in the update log, and the update stamp of the update record must be consistent with the update stamp of the directory database storage module 10 at the moment when the operation is completed. In order to query the update records whose update stamps are within a certain section range during the synchronization process between the client directory copy and the server release directory, the update records are often stored in the update log database storage module 11 in the order of update stamps in actual processing. middle.

In the implementation, due to the limitation of server physical storage capacity allocation, and the constraints of the time performance of the update synchronization process between the client and the server using the log, it is often necessary to set a capacity upper limit for the update log database storage module 11, that is, the maximum capacity How many update records to hold. When the update log database storage module 11 reaches the upper limit of capacity, when new update operation information is sent and stored, it is necessary to eliminate the oldest several update records, that is, a batch of records with the smallest update stamp to prevent the update log database storage module 11 from exceeding Capacity limitations. This may cause the update status of the client directory copy to exceed the coverage of the update log, that is, the update log cannot synchronize the client directory copy and the server release directory into a consistent update state. This solution uses compressed snapshots to solve this problem. question. The compressed snapshot here refers to a compressed information storage obtained by taking the information stored in the directory database storage module 10 as a whole through a lossless compression process. Since the content of the directory database storage module 10 will change with a series of subsequent update operations, the compressed storage of the content of the directory database storage module 10 obtained at a certain point in time is called a compressed snapshot. Obviously, the entire content of the directory database storage module 10 at the corresponding point in time can be restored by using the compressed snapshot through the decompression process, so when the update status of the client directory copy exceeds the range covered by the update log of the server's published directory, it can be used by the client. The client directly downloads the latest compressed snapshot and rebuilds the client directory copy by decompressing. In actual processing, considering the time performance of the entire upload and update operation process and from the perspective of saving storage space, it is impossible to generate a compressed snapshot every time an update operation is performed. A better way is to perform a certain number of updates cumulatively Generate a compressed snapshot after the operation. Therefore, an update increment counter can be set, the initial value is set to 0, and the counter is incremented by 1 every time a successful update operation is performed. When the count value reaches the preset threshold, a compressed snapshot is generated and the counter is cleared. In this way, as the publishing directory is continuously updated, a series of compressed snapshots will be generated and stored in the directory database compressed snapshot storage module 12 . From the perspective of access logic, the compressed snapshot storage module 12 can organize these compressed snapshots according to the stack structure, that is, the newly generated snapshots are placed on the top of the stack, and the older compressed snapshots are closer to the bottom of the stack. The purpose of this is that when a client requests to download the latest compressed snapshot, the latest compressed snapshot can be quickly found through the top of the stack. In the compressed snapshot storage module 12, the old compressed snapshots are not eliminated immediately, this is because the old compressed snapshots may be in the process of being downloaded by multiple clients, because these clients start to request to download the compressed snapshots Newer compressed snapshots have not yet been generated. So the compressed snapshot stored in the compressed snapshot storage module 12 is either up-to-date, or an old compressed snapshot that is being downloaded. Once it is detected that an old snapshot is not downloaded by the client, it can be deleted from the compressed snapshot storage module. 12 deleted.

On the basis of the above three storage modules, the function of the upload update component 13 is to write the update operation of the client to the publishing directory into the directory database storage module 10, the update log database storage module 11 and the directory database compressed snapshot storage module of the server 12. The function of the download update component 14 is to cooperate with the client, so that the client can download the catalog issued by the server to the client to generate a copy locally on the client, and keep the synchronization of the updated state with the catalog issued by the server. Specifically, update the client's copy of the publishing directory by using the update record in the update log database storage module 11 and the compressed snapshot in the directory database compressed snapshot storage module 12 according to the update status of the local publishing directory copy.

Figure 3 shows the detailed structure of the client. The client includes the following components: local directory storage module 20, snapshot download and update synchronization component 21, update task generation and submission component 22, client communication component 23, directory retrieval component 24 (optional) and directory aggregation component 25 (optional) select). The connection relationship between these components is: the client communication component 23 is respectively connected to the update task generation and submission component 22 and the snapshot download and update synchronization component 21 . The local directory storage module 20 is respectively connected to the snapshot download and update synchronization component 21 , the retrieval component 24 and the directory aggregation component 25 .

The local directory storage module 20 is used to store a copy of the directory issued by the server on the client side and the update stamp corresponding to the copy, and its data structure is consistent with that of the directory database storage module 10 of the server, see FIG. 4 . The snapshot download and update synchronization component 21 is used for downloading and publishing the catalog from the catalog publishing server, using the update log of the catalog publishing server or utilizing the compressed snapshot of the catalog publishing server to update the copy of the published information item collection catalog of the client. The update task generating and submitting component 22 is used to submit the modification operation of the client to the catalog publishing server to the catalog publishing server, which is to generate an updating task according to user operations and submit it to the catalog publishing server. The client communication component 23 is responsible for establishing a communication connection with the directory publishing server, and fulfilling the task of sending and receiving data with the server.

The client also includes an optional retrieval component 24 for performing retrieval operations in the catalog of information item collections of the client. The content of the specific retrieval operation is in the applicant's application with publication number CN101158949.

The client also includes an optional directory aggregation component 25 for performing aggregation operations on the client's information item collection directory. The directory aggregation does not involve the interaction between the server and the client, and the applicant has disclosed its specific content in the PCT application with the international application number PCT/CN2009/072520 filed on June 30, 2009. Specifically, the steps implemented by the directory aggregation component 25 are as follows: first step, set the initial result directory as a directory consisting of 0 information item sets, that is, an empty directory. In the second step, the priority order among the n source information item collection directories is set according to actual needs, and the n source information item collection directories are organized into queues according to this order, and n is greater than or equal to 1. The third step is to judge whether the queue is empty. If the queue is empty, the processing will end. The current result directory will be the final result information item collection directory. If the queue is not empty, the first element of the queue will be taken as the current source information item collection directory to be processed. , and perform team operations on the first element of the team. The fourth step is to aggregate the currently processed source information item collection directory and the current result information item collection directory into a new result information item collection directory (as the current result information item collection directory for the next cycle), and then return to the third step. The fourth step is the core, and its specific operation is to map each item set in the source information item set directory to the result information item set directory one by one in a certain order starting from the root set according to the predefined mapping rules. In each independent mapping operation, the item set being processed in the source information item set directory is called the source information item set, and the corresponding item set mapped from the source information item set to the result directory is called the target item set. There are two possible cases for each mapping operation: one case is that there is a unique target item set corresponding to the source item set in the current result directory according to the predefined mapping rules, and the mapping relationship is recorded; the other case is according to the predefined If the mapping rule does not have a target project collection corresponding to the source project collection in the current result directory, a new project collection is created in the result directory as the correspondence between the target project collection and the source project collection, and the parent collection of the new target project collection is specified Map the parent collection of the source project collection in the source directory to the corresponding target project collection in the result directory, and record this mapping relationship. In order to achieve the catalog requirement of aggregated information items: the directly affiliated items contained in the source item set become the directly affiliated items of the target item set.

In the specific implementation, for a source project set, it is necessary to find a unique target project set whose connotation is consistent with it in the result directory, and gather the directly subordinate projects in the source project set into the target project set. The standard for judging whether the connotation of the target item set is consistent with the source item set is the predefined mapping rule. For example, in practical applications, each information item set has a name representing its connotation. The information item set used to store video information items is named "Video", and the information item set used to store audio information items is named "Video". "Audio", etc., no two project collections with the same name can exist in one collection directory. Therefore, the same-name mapping rule can be predefined, that is, find the item set with the same name as the source item set in the result directory as the corresponding target item set, and gather the directly subordinate items into the target item set. If no project collection with the same name is found in the current result directory, it means that there is no project collection with the same connotation as the source project collection in the current result directory, and a new project collection with the same name needs to be created in the result directory and the source The projects directly subordinate to the project collection are aggregated into it.

The overall effect of doing this is to bring together the items contained in multiple consistent information item collections from multiple source information item collection directories into a unified item collection in the result directory, where these items can be aggregated. Information items from different information sources but belonging to the same connotation are retrieved as a whole.

The process of client upload update operation

Fig. 6 shows the process of the client uploading the update operation. This process is mainly completed by the cooperation of the update task generation and submission component 22 of the client and the upload update component 13 of the directory publishing server. First, the update task generating and submitting component 22 of the client converts and generates an update task according to the user interface operation data (an update task can be regarded as an update operation sequence composed of multiple update operations), and then sends the update task to the server. Each publishing directory on the server side has a corresponding update task queue. After receiving the update task from the client, the server puts it at the end of the corresponding update task queue for processing. Another update task processing program takes out the update task from the head of the update task queue in turn, updates the release directory stored in the directory database storage module 10 according to the sequence of multiple update operations in the update task, and after each successful update operation, the corresponding The update stamp plus one. Subsequently, the update operations performed successfully in the update task are marked with corresponding update stamps according to the update order, and recorded in the update log (stored in the update log database storage module 11) (ie, the step of writing the update log). After writing the update log, the server sends back the execution result of the update task to the client (possible information includes: which update operations in the update task are executed successfully, which update operations fail to execute, etc.), and the client performs some processing on the result after receiving the execution result , for example: a prompt box pops up to inform the user which update operations failed.

After the execution result of the update task is sent back, the increment of the update stamp of the directory database by this update task is accumulated into an update increment counter. When this counter exceeds the preset threshold, the counter is cleared, and the current content of the directory database storage module 10 is compressed as a whole to generate a compressed snapshot, and then the compressed snapshot is pushed into the stack structure of the directory database compressed snapshot storage module 12 top of the stack.

The process by which a client downloads a server-published catalog to update its local copy of the catalog

Fig. 7 shows the process of the client downloading the catalog published by the server. This process is completed jointly by the download and update component 14 of the directory publishing server and the snapshot download and update synchronization component 21 of the client. First, the client creates a timer, and the timer triggers the update status checking process according to a certain time interval: the client requests the catalog publishing server to query the current update status of the corresponding published catalog, including the current update stamp of the published catalog (that is, the catalog database storage module 10), the update stamp range of the update log record (i.e. the latest update stamp and the oldest update stamp of the update record in the update log database storage module 11), and then compare it with the update state of the local directory copy, There are three situations as follows. The first case is that the update stamp of the copy of the local directory is equal to the update stamp of the directory published by the server, that is, the update status of the two is consistent, then return to the timer program, wait for a period of time, and then check the update status. The second situation is that the local directory copy is older than the release directory (that is, the update stamp of the local directory copy is older than the update stamp of the release directory) and the required update incremental log is within the record range of the update log database storage module 11 (similarly Take the method of comparing the update stamps), then download the required update incremental log, and then update the local directory copy in the order of the update stamps of the update log entries until the update status of the local directory copy is the same as the update status of the published directory at the previous check unanimous. Considering that the client may encounter new updates (possibly from other clients or from this client) while performing the above process, the publishing directory may encounter new updates, so the subsequent process turns to querying the update status of the publishing directory. The 3rd kind of situation is that the local directory copy is older than the server's published directory but the required update incremental log is not within the record range of the update log database storage module 11 (this situation includes a special situation: the client has not yet established a local directory status of the copy). In this case, the client cannot use the changelog to update the local directory copy, so it needs to download the latest compressed snapshot of the database of the server-published directory and uncompress it to rebuild the local directory copy. The compressed snapshot of the directory database newly created by the directory publishing server is always placed at the top of the stack structure of the directory database compressed snapshot storage module 12, and when the client requests the latest directory compressed snapshot, only the compressed snapshot at the top of the stack is sent to client. Considering that non-latest compressed snapshots may also be downloaded, a phase-out mechanism is adopted for non-top compressed snapshots.

For ease of understanding, examples of the above three cases are as follows: Assume that a natural number serial number is used as the update stamp, and the update stamp of a publishing directory on the current server is 216, and the update stamp range of the corresponding update log is 101 to 216 (according to The above description of the update stamp in this case shows that the update stamp of the current published directory must be consistent with the upper limit of the update stamp of the update log). If the update stamp of a client's local copy of the directory is 216, the update status of the client's local copy of the directory is consistent with that of the published directory through comparison with the update stamp of the server's published directory. This is the first case described in the previous paragraph. If the update stamp of the client's local directory copy is within the range of 100 to 215 (that is, greater than or equal to 100 and less than or equal to 215), it is obviously not equal to the update stamp of the published directory, and then the update stamp is increased by 1 (plus The purpose of 1 is to obtain the lower limit of the update stamp of the required incremental update record. For example, the update stamp of the client's local directory copy is 100, and the update stamp range of the update log records required to update the local directory copy is 101 to 216 ) is compared with the range of update log update stamps to obtain a result that matches the second case described in the previous paragraph. If the update stamp of the client's local copy of the directory is less than 100, it can be determined that the update status of the client's local copy of the directory is neither equal to the update status of the server's published directory, nor is it within the range covered by the update log. Case 3 described in the previous paragraph.

The above-mentioned embodiments are provided for those of ordinary skill in the art to implement or use the present invention. Those of ordinary skill in the art can make various modifications or changes to the above-mentioned embodiments without departing from the inventive idea of the present invention. Therefore, the present invention The scope of protection of the invention is not limited by the above-mentioned embodiments, but should be the maximum scope consistent with the innovative features mentioned in the claims.

Claims (7)

1. the delivery system of an information project catalog aggregator comprises:

The catalogue publisher server further comprises:

The catalog data base memory module is used for storage and comprises: the information project catalog aggregator that is published, the corresponding renewal of this catalogue are stabbed;

Upgrade the log database memory module, be used for the each successful renewal operation of the information project catalog aggregator that is published stamped to upgrade stabbing, and it is stored as a more new record;

Upload the renewal assembly; Connect the catalog data base memory module and upgrade log database memory module and catalog data base compression snapshot memory module; Client is updated to the catalog data base memory module to the renewal operation of the information project catalog aggregator that is published and the information of the renewal operation of success is saved to upgrade the log database memory module, and when the renewal number of operations of the success of current accumulative total surpasses predetermined threshold value, generate one and compress snapshot and be saved to catalog data base and compress the snapshot memory module with the current content of catalog data base memory module;

Catalog data base compression snapshot memory module connects to upload and upgrades assembly and down loading updating assembly, is used for the compression snapshot of the content of storage directory database storing module;

The down loading updating assembly; Connect and upgrade log database memory module and catalog data base compression snapshot memory module; Utilize the more new record and the catalog data base that upgrade in the log database memory module to compress the compression snapshot in the snapshot memory module, the fit end upgrades the copy of the information project catalog aggregator that is published of client;

The server end communications component is used for establishing a communications link with client, fulfils the task of carrying out data transmit-receive with client;

Client, mutual through communication channel and this catalogue publisher server, further comprise:

The local directory memory module is used for comprising in client stores: the copy of the information project catalog aggregator that is published, the renewal that this copy is corresponding are stabbed;

Snapshot is downloaded and is upgraded Synchronization Component, connects the local directory memory module, utilizes the renewal daily record of catalogue publisher server or utilizes the copy of the information project catalog aggregator that is published of the compression snapshot update client of catalogue publisher server;

Updating task generates and submits to assembly, operates generating updating task and being committed to the catalogue publisher server according to the user;

Client communication component establishes a communications link with the catalogue publisher server, fulfils the task of carrying out data transmit-receive with server.

2. the delivery system of information project catalog aggregator according to claim 1 is characterized in that, this catalog data base memory module further comprises:

Information project set storage unit is the attribute regulation of the set membership between other information project set, this information project set in its sign of each information project set record in the information project catalog aggregator, this information project set and the information project catalog aggregator and the satellite information of other this information project set;

The information project storage unit, the information project set that it identifies for each information project record in the information project catalog aggregator, this information project is subordinate to, attribute and the attribute value of correspondence and the satellite information of other this information project that this information project has;

Upgrade and stab the unit, the renewal of record catalog data base memory module institute canned data project set catalogue is stabbed.

3. the delivery system of information project catalog aggregator according to claim 1 is characterized in that, upgrades many records that have the following information of record in the log database memory module: upgrade stamp, object type, sign, action type, operating parameter.

4. the delivery system of information project catalog aggregator according to claim 1 is characterized in that, this delivery system also comprises:

Retrieval component connects the local directory memory module, is used for doing search operaqtion at the information project catalog aggregator of client.

5. the delivery system of information project catalog aggregator according to claim 1 is characterized in that, this delivery system also comprises:

The catalogue polymerizing component connects the local directory memory module, is used for the information project catalog aggregator of client is done converging operation.

6. the dissemination method of an information project catalog aggregator, dissemination method comprise that client uploads the process of upgrading operation and client downloads server issue catalogue upgrading the process of local directory copy,

Client is uploaded the process of upgrading operation and is further comprised:

Operating user interface according to client generates a updating task;

This updating task is committed to server;

Server is according to this updating task that receives; Many that comprise according to this task are upgraded the operation informations corresponding issue catalogue of this task of update service device successively; And when upgrading successfully, unit of increase is stabbed in the renewal of catalogue at every turn; And this is upgraded operation information stamp catalogue renewal this moment and stab to be saved to and upgrade daily record and form a more new record, upgrade daily record and stab through upgrading that to issue catalogue related with server;

If the successful renewal number of operations of the current accumulative total that this catalogue is corresponding surpasses predetermined threshold value, should issue catalogue and do a compression of reduced overall generation snapshot, and the successful renewal number of operations zero clearing of the current accumulative total that this catalogue is corresponding;

Client downloads server issue catalogue further comprises with the process of upgrading the local directory copy:

The current update mode of client-requested querying server issue catalogue comprises the renewal stamp scope that the current renewal of server issue catalogue is stabbed and upgraded daily record;

The renewal that server is issued catalogue is stabbed and the renewal of upgrading daily record stab scope and the renewal of the local directory copy of client stab compare after; Select a kind of mode to upgrade the local directory copy in the down loading updating daily record with downloading in the compression snapshot dual mode, wherein divide three kinds of situation to carry out catalogue and upgrade:

If the renewal of local directory copy is stabbed the renewal equal server issue catalogue and stabbed, upgrade the comparison of stamp after then waiting for one preset period again;

Old renewal in server issue catalogue is stabbed and required renewal operates in the renewal stamp scope of upgrading daily record if the renewal of local directory copy is stabbed, and then downloads required renewal daily record, the sequential update local directory copy that stabs according to the renewal of upgrading daily record again;

Old renewal in server issue catalogue is stabbed and required renewal is operated in the renewal stamp scope of not upgrading daily record if the renewal of local directory copy is stabbed, and then downloads compression snapshot and decompression to rebuild the local directory copy.

7. the dissemination method of information project catalog aggregator according to claim 6 is characterized in that, the more new record that upgrades in the daily record comprises: upgrade stamp, object type, sign, action type, operating parameter.

Images