Abstract: When a software component is starting, such as but not limited to a task or a subtask, the component pushes its identification (ID) onto a stack. The component executes its other instructions. If the component completes its instructions so that it can terminate normally, it pops the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, it will not be able to pop the stack so its ID will remain in the stack. Another software process can read the IDs in the stack to identify which components have failed and can automatically take a specified action, such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: Techniques for dynamic domain-based isolation are described. An apparatus may comprise a domain name component operative to receive a domain name request for a uniform resource locator, the domain name component operative to resolve the domain name request 105 on a wildcard entry in a domain name table, a receiving component operative to receive a request for a web application at the uniform resource locator, the uniform resource locator having been dynamically assigned to the web application, and an application identification component operative to determine which hosted web application of a plurality of hosted web applications corresponds to the requested web application on the basis of the uniform resource locator. Other embodiments are described and claimed.

Abstract: Techniques for dynamic domain-based isolation are described. An apparatus may comprise a domain name component operative to receive a domain name request for a uniform resource locator, the domain name component operative to resolve the domain name request 105 on a wildcard entry in a domain name table, a receiving component operative to receive a request for a web application at the uniform resource locator, the uniform resource locator having been dynamically assigned to the web application, and an application identification component operative to determine which hosted web application of a plurality of hosted web applications corresponds to the requested web application on the basis of the uniform resource locator. Other embodiments are described and claimed.

Abstract: When a software component is starting, such as but not limited to a task or a subtask, the component pushes its identification (ID) onto a stack. The component executes its other instructions. If the component completes its instructions so that it can terminate normally, it pops the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, it will not be able to pop the stack so its ID will remain in the stack. Another software process can read the IDs in the stack to identify which components have failed and can automatically take a specified action, such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: Disclosed herein are systems, methods, and software for facilitating technology upgrades. In at least one implementation, an incomplete upgrade to service units within a service environment is initiated. An upgrade health of each of the service units is evaluated based at least in part on results of the incomplete upgrade. A complete upgrade of the service environment is then initiated based at least in part on the upgrade health of each of the plurality of service units.

Abstract: Techniques for dynamic domain-based isolation are described. An apparatus may comprise a domain name component operative to receive a domain name request for a uniform resource locator, the domain name component operative to resolve the domain name request 105 on a wildcard entry in a domain name table, a receiving component operative to receive a request for a web application at the uniform resource locator, the uniform resource locator having been dynamically assigned to the web application, and an application identification component operative to determine which hosted web application of a plurality of hosted web applications corresponds to the requested web application on the basis of the uniform resource locator. Other embodiments are described and claimed.

Abstract: A conflict resolution system is described for reducing false conflicts among entities synchronized within a content management system. A typical content management system maintains a version for an entity that is incremented each time an endpoint modifies the entity, including changes that affect the metadata rather than the content of the entity. The conflict resolution system adds a new content version that is updated when the content of the entity changes. By comparing content version information, endpoints can automatically resolve false conflicts that occur when an endpoint has modified the metadata of the entity.

Abstract: A cloud manager is utilized in the patching of physical machines and virtual machines that are used within an online service, such as an online content management service. The cloud manager assists in the scheduling of the application of software patches to the machines (physical and virtual) within the network such that the availability of the online service is maintained while machines are being patched. The machines to be patched are partitioned into groups that are patched at different times. Generally, the groups are partitioned into a highly available independent groups of machines such that one or more of the groups that are not currently being patched continue to provide the service(s) of the group that is being patched. The machines (physical and virtual) within each of the groups may be patched in parallel.

Abstract: A conflict resolution system is described for reducing false conflicts among entities synchronized within a content management system. A typical content management system maintains a version for an entity that is incremented each time an endpoint modifies the entity, including changes that affect the metadata rather than the content of the entity. The conflict resolution system adds a new content version that is updated when the content of the entity changes. By comparing content version information, endpoints can automatically resolve false conflicts that occur when an endpoint has modified the metadata of the entity.

Abstract: A conflict resolution system is described for reducing false conflicts among entities synchronized within a content management system. A typical content management system maintains a version for an entity that is incremented each time an endpoint modifies the entity, including changes that affect the metadata rather than the content of the entity. The conflict resolution system adds a new content version that is updated when the content of the entity changes. By comparing content version information, endpoints can automatically resolve false conflicts that occur when an endpoint has modified the metadata of the entity.