Transaction query engine
View Patent ↗Example implementations described herein are directed to a transaction query engine involving a token that is generated by the server and sent to the corresponding the client. The client uses the token to query transactions made on the server. The token can include mountpoint information detailing shared and private information of the filesystems, transaction identifiers identifying transactions of a filesystem, and a filesystem identifier to identify the corresponding filesystem. The server processes this token and updates the token based on the transaction information of the filesystem, and sends the token back to the corresponding client.
1. A server comprising:
a memory configured to manage a private file system for a first user and a shared file system which is shared by a plurality of users including the first user, wherein the shared file system is pointed from the private file system;
a processor, configured to:
create a single token comprising first transaction information indicative of one or more transactions that occurred on the private file system and second transaction information indicative of one or more transactions that occurred on the shared file system;
send the single token to a client device corresponding to the first user; and
receive a request, which is created based on the single token by the client device and requests to obtain a combined transaction log comprising a first transaction log of the private file system and a second transaction log of the shared file system, from the client device;
wherein the first transaction information comprises a first file system identifier of the private file system, a first mount point of the private file system, and a first transaction ID associated with a transaction that is not reflected on data of the client device;
wherein the second transaction information comprises a second file system identifier of the shared file system, a second mount point of the shared file system, and a second transaction ID associated with a transaction that is not reflected on data of the client device.
2. The server of claim 1 , wherein the processor is further configured to send the combined transaction log.
3. The server claim 1 , wherein the memory is further configured to manage the combined transaction log as a combination of a first transaction log of the private file system and a second transaction log of the shared file system.
4. The server of claim 1 , wherein the processor is further configured to create another single token that omits the second transaction information when the shared folder becomes unshared with the first user after creating the single token.
5. The server of claim 1 ,
wherein the memory is further configured to manage another shared file system which becomes shared with the first user after creating the single token;
wherein the processor is further configured to create another single token comprising third transaction information indicative of one or more transactions that occurred on the another shared file system.
6. A method, comprising:
managing a private file system for a first user and a shared file system which is shared by a plurality of users including the first user, wherein the shared file system is pointed from the private file system;
creating a single token comprising first transaction information indicative of one or more transactions that occurred on the private file system and second transaction information indicative of one or more transactions that occurred on the shared file system;
sending the single token to a client device corresponding to the first user; and
receiving a request, which is created based on the single token by the client device and requests to obtain a combined transaction log which includes a first transaction of the private file system and a second transaction log of the shared file system, from the client device;
wherein the first transaction information comprises a first file system identifier of the private file system, a first mount point of the private file system, and a first transaction ID associated with a transaction that is not reflected on data of the client device;
wherein the second transaction information comprises a second file system identifier of the shared file system, a second mount point of the shared file system, and a second transaction ID associated with a transaction that is not reflected on data of the client device.
7. The method of claim 6 , further comprising sending the combined transaction log.
8. The method of claim 6 , further comprising managing the combined transaction log as a combination of a first transaction log of the private file system and a second transaction log of the shared file system.
9. The method of claim 6 , further comprising creating another single token that omits the second transaction information when the shared folder becomes unshared with the first user after creating the single token.
10. The method of claim 6 , further comprising:
managing another shared file system which becomes shared with the first user after creating the single token; and
creating another single token comprising third transaction information indicative of one or more transactions that occurred on the another shared file system.