Microsoft Technology Licensing, LLC

Maxim Lukiyanov

Arshish C Kapadia

Tarkan Sevilmis

Tittu Jose

Hardik V Shah

Sreekanth Lingannapeta

Gheorghita Irimescu

Janak Madhusudan Agarwal

Stephen John Clark

Jay R Rathi

Dean Justus

Yina Arenas

Sujata Suresh Adgaonkar

Betty Cheuk Man Yip

Dale Rector

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.

Failure mode identification and reporting

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 requeston 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.

Techniques for dynamic domain-based isolation

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 then executes () its other instructions. If the component completes its instructions so that it can terminate normally (), then 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, 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 () 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.

Growing community of inventors

Redmond, WA, United States of America

Maxim Lukiyanov