Abstract: Technologies support virtual expansion of object containers and of individual large objects in a cluster. Some examples provide scalable object service blob container overflow using multiple clustered shared volumes. One or more of the following may overflow from one cluster volume to another: multiple individual data objects of a container, at least one section of a data object of the container, metadata of at least one object of the container, system metadata of the container. The overflow may be hidden by maintaining a flat namespace outside the cluster.

Abstract: An application instance identifier is employed with various systems and methods in order to provide a requestor with continuous access to a resource when operating in a client clustered environment. A requestor residing on a first client may attempt to access a resource. The first client sends a request to access the resource. The request may be associated with an application instance identifier that identifies the requestor. At some point, the first client fails and the requestor is associated with a second client via a failover mechanism. The second client sends a second request to access the resource on behalf of the requestor. The second request is associated with the requestor's application instance identifier. The application instance identifier is used to identify the second request as belonging to the same requestor as the first request, thereby granting the second request to access the resource while avoiding a conflict situation.

Abstract: An application instance identifier is employed with various systems and methods in order to provide a requestor with continuous access to a resource when operating in a client clustered environment. A requestor residing on a first client in may attempt to access a resource. The first client sends a request to access the resource. The request may be associated with an application instance identifier that identifiers the requestor. At some point, the first client fails and the requestor is associated with a second client via a failover mechanism. The second client sends a second request to access the resource on behalf of the requestor. The second request is associated with the requestor's application instance identifier. The application instance identifier is used to identify the second request as belonging to the same requestor as the first request, thereby granting the second request to access the resource while avoiding a conflict situation.

Abstract: A hybrid environment may be used for addressing application compatibility between a host operating system and one or more application(s) optimized to run on a different (“guest”) version of the host operating system. A thunking wrapper consisting of a native thunking layer, a service thunking layer, and a subsystem thunking layer provides translation between the guest application and the host operating system for a seamless interface. Multiple thunking wrappers may be included to support application compatibility between multiple guest operating systems and the host operating system.

Abstract: A method for testing a software shim is provided, in which a skeleton executable file is altered so that it mimics the executable file for which the shim is intended. The alterations made to the skeleton executable file may include one or more of the following: changing the file name, padding the file and changing the calculated checksum of the file.

Abstract: A hybrid environment may be used for addressing application compatibility between a host operating system and one or more application(s) optimized to run on a different (“guest”) version of the host operating system. A thunking wrapper consisting of a native thunking layer, a service thunking layer, and a subsystem thunking layer provides translation between the guest application and the host operating system for a seamless interface. Multiple thunking wrappers may be included to support application compatibility between multiple guest operating systems and the host operating system.

Abstract: An application program interface (API) replay tool and method is disclosed for modeling and testing APIs. The replay tool receives as input a set of API calls and associated context information and resources. A set of components are called to map variables and a context into the replay tool environment. An API builder translates the original API call (including mapping memory references of parameters) into a sequence of assembly code instructions, constituting the replayed API call, which is placed in an execution buffer. The execution buffer is thereafter executed in a replay environment including a set of resources extracted from a source binary file associated with the replayed API. Thereafter, the operating system, or other suitable consumer of API calls, executes the call in the context recreated by the API replay tool prior to passing the call.

Abstract: A method for testing a software shim is provided, in which a skeleton executable file is altered so that it mimics the executable file for which the shim is intended. The alterations made to the skeleton executable file may include one or more of the following: changing the file name, padding the file and changing the calculated checksum of the file.