Loading of server-stored user profile data

• US 7,792,934 B2
• Filed: 01/02/2008
• Issued: 09/07/2010
• Est. Priority Date: 01/02/2008
• Status: Active Grant

• Current Assignee: Cloud Software Group Switzerland GmbH
• Original Assignee: Citrix Systems International GmbH (Cloud Software Group)
• Inventors: Klein, Helge
• Primary Examiner(s): Chan; Wing F
• Assistant Examiner(s): Yi; David
• Application Number:
  US11/968,361
• Publication Number:
  US 20090172160A1
• Time in Patent Office: 979 Days
• Field of Search: 709223-225
• US Class Current: 709/222
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation

Abstract

One or more computer-implemented methods provided by computer-readable media for providing and loading user profile data from a server computer system to a client computer system may be used together with the server and client computer systems. The client computer system may be caused to initiate a login process for a user on the client computer system and to send login information to the server during the login process. After reception of the login information from the client, the server evaluates the received login information to obtain user information corresponding to a user identified in the login information. Based on the obtained user information, the server finds user profile data stored on the server computer system. Finally, metadata relating to the user profile data may be determined by the client computer system by pulling corresponding data from the server computer system.

Claims

1. A method that, when executed on a processor of a client computer system, causes the client computer system to perform a method of loading user profile data from a server computer system to the client computer system, the method comprising:

initiating a login process for a user on the client computer system;

during the login process, sending login information to the server computer system;

determining metadata relating to the user profile data;

parsing the metadata related to the user profile data, wherein the user profile data comprises at least one file;

creating a stub for each file of the user profile data identified by the parsed metadata; and

determining whether a file system of the client computer system supports reparse points;

if the file system supports reparse points, creating, for each file of a user profile, a reparse point to store at least a path to a location on the server computer system containing a file of the user profile data, and

if the file system does not support reparse points, loading and initiating a driver simulating the functionality of reparse points.

2. The method of claim 1, wherein determining metadata further comprise pulling file information corresponding to the user profile data from the server computer system and determining the metadata from the pulled information.

3. The method of claim 1, further comprising:

completing the login process on the client computer system without reception of the complete user profile data.

4. The method of claim 1, further comprising:

requesting partial profile data being at least a part of the user profile data from the server computer system, if an entity running on the client computer system requires access to the partial profile data; and

receiving the requested partial profile data from the server computer system.

5. The method of claim 1, further comprising:

determining whether an application on the client computer system requests access to a file of the user profile data; and

determining whether a stub exists for the requested file;

if only a stub exists for the requested file;

pausing the request; and

downloading the remaining file data for the requested file from the server computer.

6. The method of claim 1, further comprising:

downloading, from the server computer system, remaining file data for each user profile file represented by a stub.

7. The method of claim 6, further comprising:

detecting that the client computer system is idle;

wherein downloading remaining file data comprises downloading, from the server computer system, remaining file data for each user profile file represented by a stub while the client is idle.

8. The method of claim 1, wherein sending login information further comprises sending, to the server computer, an indication that only the metadata relating to the user profile data is to be sent, and wherein the method further comprises:

receiving metadata relating to the user profile data from the server computer system;

wherein determining metadata comprises determining metadata relating to the user profile data from the received metadata.

9. The method of claim 1, further comprising:

determining whether the user is having a server-stored user profile;

if the user is having a server-stored user profile, requesting the metadata relating to the user profile data; and

if the user is not having a server-stored user profile, loading user profile data stored local to the client computer system.

10. The method of claim 1, further comprising:

uploading, to the server computer system, the user profile data of the client computer system, if the user profile data has been modified on the client computer system.

11. A method that, when executed by a processor of a server computer system, causes the server computer system to perform a method of providing user profile data from the server computer system to a client computer system, the method comprising:

receiving login information from the client computer system;

evaluating the received login information to obtain user information corresponding to a user identified in the login information;

finding user profile data stored on the server computer system based on the obtained user information;

providing data relating to the user profile data to the client computer system to determine metadata relating to the user profile data, wherein the user profile data comprises at least one file;

parsing the metadata related to the user profile data; and

creating a stub for each file of the user profile data identified by the parsed metadata;

wherein the client computer system determines whether a file system of the client computer system supports reparse points,

and one of either creates a reparse point for each file of a user profile when the file system supports reparse points, and loads and initiates a driver simulating the functionality of reparse points when the file system does not support reparse points.

12. The method of claim 11, wherein evaluating the received login information further comprises determining whether the login information contains an indication to only provide metadata relating to the user profile data, and wherein the method further comprises:

sending metadata to the client computer system, if the login information does include an indication to only provide metadata; and

sending complete user profile data to the client computer system, if the login information does not include an indication to only provide metadata.

13. The method of claim 11, wherein the user profile data comprises at least one file, and wherein the method further comprises:

receiving, from the client computer system, a request for at least one complete file of the user profile data; and

sending the at least one complete file to the client computer system.

14. A client computer system for loading user profile data from a server computer system, comprising:

a processor;

a memory operatively coupled to the processor;

a network interface configured to establish a connection to another computer system via a network;

a login module configured to allow a user to log in to the client computer system, and to send login information to a server computer system during the login process; and

a service module executed by the processor and configured to determine metadata relating to the user profile data comprising at least one file, and create a stub for each file of the user profile data identified by metadata relating to the user profile data, the metadata parsed by a metadata parser,

the service module determining whether a file system of the client computer system supports reparse points, and

one of either creates a reparse point for each file of a user profile when the file system supports reparse points, and loads and initiates a driver simulating the functionality of reparse points when the file system does not support reparse points.

15. The client computer system of claim 14, wherein

the metadata parser executes on the client computer system to parse the received metadata relating to the user profile data.

16. The client computer system of claim 14, further comprising:

a program, executed by the processor, configured to access partial profile data being at least a part of the user profile data;

wherein the service module is further configured to request the partial profile data from the server computer system, and wherein the service module is further configured to receive the requested partial profile data and replace the stub with the received partial profile data.

17. A server computer system for maintaining user profile data, comprising:

a processor;

a memory operatively coupled to the processor;

a network interface configured to establish a connection to another computer system via a network;

a user profile store configured to store at least one user profile; and

a service module executed by the processor and configured to request user profile data from the user profile store, wherein the service module is further configured to provide, via the network link, data relating to the requested user profile data to a client computer system to determine metadata relating to the user profile data,

wherein the client computer system;

parses the metadata relating to the user profile data, wherein the user profile data comprises at least one file,

creates a stub for each file of the user profile data identified by the parsed metadata,

determines whether a file system of the client computer system supports reparse points, and

one of either creates a reparse point for each file of a user profile when the file system supports reparse points, and loads and initiates a driver simulating the functionality of reparse points when the file system does not support reparse points.

18. The server computer system of claim 17, wherein the service module is further configured to receive login information from the client computer system prior to requesting the user profile data, and wherein the service module is further configured to determine the user profile data based on the login information.