Abstract: Architecture that employs an abstraction of a mailbox store that allows clients to connect to alternate mailboxes associated with a single mail-enabled user, using the same mechanism the user utilizes to connect to the user's main mailbox. On top of this basic infrastructure, new features can be built, including server-hosted e-mail archives and mailboxes mirrored from other e-mail systems. In support thereof, the architecture also includes a mechanism for mailboxes to expose all or only a subset of mailbox features, and to advertise which mailbox features are supported.

Abstract: Architecture that provides an abstraction of a mailbox store that allows clients to connect to multiple “alternate” mailboxes associated with a single user, exposing the same mechanism used to connect to a user's main mailbox. Beneath this abstraction, support for alternate mailboxes is implemented as a folder hierarchy contained within the user's own mailbox or another physical mailbox. The architecture uses a sub-mailbox folder hierarchy to virtualize a separate physical mailbox. On top of this basic infrastructure, other features can be built such as server-hosted e-mail archives and mailboxes mirrored from other e-mail and PIM data systems. In support thereof, a mechanism is provided for an abstraction layer to expose all or a subset of the alternate mailbox features, and to advertise which alternate mailbox features are supported per alternate mailbox.

Abstract: Described is a technology by which application-related resources are differentiated from other types of resources via a uniform resource identifier (URI) associated with each resource. Application-related resources may include a resource embedded in the application program, at least one content file associated with (e.g., distributed with) the application program, or a resource located on a site from which the application program was deployed. Because of the URI, a creating/loading mechanism may be called using substantially similar calling code to that which is used to call the mechanism for loading another type of resource, thereby providing a consistent programming model. In one example, the URI includes a packaging scheme and authority, or a relative path which may be converted to an absolute URI. The mechanism creates an object corresponding to the application-related resource, and loads the resource or a stream of a compound resource.

Abstract: Architecture that provides an abstraction of a mailbox store that allows clients to connect to multiple “alternate” mailboxes associated with a single user, exposing the same mechanism used to connect to a user's main mailbox. Beneath this abstraction, support for alternate mailboxes is implemented as a folder hierarchy contained within the user's own mailbox or another physical mailbox. The architecture uses a sub-mailbox folder hierarchy to virtualize a separate physical mailbox. On top of this basic infrastructure, other features can be built such as server-hosted e-mail archives and mailboxes mirrored from other e-mail and PIM data systems. In support thereof, a mechanism is provided for an abstraction layer to expose all or a subset of the alternate mailbox features, and to advertise which alternate mailbox features are supported per alternate mailbox.

Abstract: Navigating through pages of content. In aspects, a state machine is provided that simplifies navigating. The state machine allows multiple navigation services to work together in a hierarchical manner to obtain content. The state machine also provides a mechanism for stopping navigation and responding to errors.

Abstract: Architecture that employs an abstraction of a mailbox store that allows clients to connect to alternate mailboxes associated with a single mail-enabled user, using the same mechanism the user utilizes to connect to the user's main mailbox. On top of this basic infrastructure, new features can be built, including server-hosted e-mail archives and mailboxes mirrored from other e-mail systems. In support thereof, the architecture also includes a mechanism for mailboxes to expose all or only a subset of mailbox features, and to advertise which mailbox features are supported.

Abstract: Techniques to manage email personal archives are described. A computer-implemented system may comprise a primary mailbox component, associated with a user, and operative to receive and send email. The computer-implemented system may further comprise an alternate mailbox component separate from the primary mailbox component and associated with the user and the primary mailbox, operative to store email. The computer-implemented system may also include a mail client operative on a client computer to access and display contents of the primary and alternate mailboxes substantially simultaneously. Other embodiments are described and claimed.

Abstract: Described is a technology by which a managed web browser control hosts an unmanaged web OLE control to control navigation requests by the unmanaged web OLE control on behalf of partially trusted code. Site locking may be performed to constrain a site to navigation only to other pages within its site, thereby preventing navigation to an undesirable location. In one example, the unmanaged web OLE control communicates information corresponding to a navigation request to the managed web browser control, and the managed web browser control processes the information to establish whether the navigation is to be allowed or blocked. The benefits of site-locking with respect to privacy are also described, as is z-order management to protect against site spoofing.

Abstract: Described is a method and system by which document servers/applications (document objects) hosted by the browser may integrate with the browser's travel log. As a result, the user can use browser navigation commands, particularly forward and back commands, as well as a drop-down list of entries, to navigate among a hosted document's pages. Integration also allows the document object to add travel entries, persist relevant state, delete travel entries and update existing travel entries with new state. The browser and document object may communicate to update the browser's address bar, and to communicate various navigation events to keep each other synchronized. In one implementation, the browser limits navigation to top-level travel entries and the sub-navigation entries of the currently hosted document object, by filtering out sub-navigation entries that do not correspond to the currently-hosted document object. Frames no longer valid are also filtered from those available for navigation.

Abstract: Described is a technology by which application-related resources are differentiated from other types of resources via a uniform resource identifier (URI) associated with each resource. Application-related resources may include a resource embedded in the application program, at least one content file associated with (e.g., distributed with) the application program, or a resource located on a site from which the application program was deployed. Because of the URI, a creating/loading mechanism may be called using substantially similar calling code to that which is used to call the mechanism for loading another type of resource, thereby providing a consistent programming model. In one example, the URI includes a packaging scheme and authority, or a relative path which may be converted to an absolute URI. The mechanism creates an object corresponding to the application-related resource, and loads the resource or a stream of a compound resource.