Abstract: Stacks that associate different electronic content are created using tags that are associated with electronic content. Stacks may be personal, organizational and/or shared. A tag may be associated with different types of electronic content (e.g. documents, people, contacts, meetings, emails, . . . ) that may be stored in different locations. The tag acts as an identifier that travels with the content as the electronic content is used. Content may be automatically/manually tagged. As the tagged content is used, the different applications that interact with the content (e.g. a messaging application, a content application) can use the tag to perform different actions. Changes to content with a tag may be aggregated such that users looking at the “consolidated” view can see all changes made to content or activity related to that content.

Abstract: A link to a file to be stored at a network location is calculated using a client before the file is uploaded to the network location. The client may calculate the link to the network location either while online or offline. In response to determining to upload a file, a link to the file at the network location is calculated before uploading the file. The created link may be a direct link that specifies the file at the network location as the destination of the link and/or a redirect link that when used redirects the user to the file at the network location. The link may be created using various information (e.g. a default location, filename, and/or a unique key). When online, the client may reserve a specific link with the network location before the file is uploaded.

Abstract: A link to a file to be stored at a network location is calculated using a client before the file is uploaded to the network location. The client may calculate the link to the network location either while online or offline. In response to determining to upload a file, a link to the file at the network location is calculated before uploading the file. The created link may be a direct link that specifies the file at the network location as the destination of the link and/or a redirect link that when used redirects the user to the file at the network location. The link may be created using various information (e.g. a default location, filename, and/or a unique key). When online, the client may reserve a specific link with the network location before the file is uploaded.

Abstract: A link to a file to be stored at a network location is calculated using a client before the file is uploaded to the network location. The client may calculate the link to the network location either while online or offline. In response to determining to upload a file, a link to the file at the network location is calculated before uploading the file. The created link may be a direct link that specifies the file at the network location as the destination of the link and/or a redirect link that when used redirects the user to the file at the network location. The link may be created using various information (e.g. a default location, filename, and/or a unique key). When online, the client may reserve a specific link with the network location before the file is uploaded.

Abstract: Stacks that associate different electronic content are created using tags that are associated with electronic content. Stacks may be personal, organizational and/or shared. A tag may be associated with different types of electronic content (e.g. documents, people, contacts, meetings, emails, . . . ) that may be stored in different locations. The tag acts as an identifier that travels with the content as the electronic content is used. Content may be automatically/manually tagged. As the tagged content is used, the different applications that interact with the content (e.g. a messaging application, a content application) can use the tag to perform different actions. Changes to content with a tag may be aggregated such that users looking at the “consolidated” view can see all changes made to content or activity related to that content.

Abstract: A link to a file to be stored at a network location is calculated using a client before the file is uploaded to the network location. The client may calculate the link to the network location either while online or offline. In response to determining to upload a file, a link to the file at the network location is calculated before uploading the file. The created link may be a direct link that specifies the file at the network location as the destination of the link and/or a redirect link that when used redirects the user to the file at the network location. The link may be created using various information (e.g. a default location, filename, and/or a unique key). When online, the client may reserve a specific link with the network location before the file is uploaded.