VERSION RESILIENCY FOR A HOST APPLICATION AND MANAGED CODE
First Claim
1. A method for providing version resiliency between a host application that is unmanaged code and managed code, the host application and the managed code communicating via an adapter and a proxy that implement a protocol, by a method comprising:
- when a new version of the host application that impacts an interface exposed by an object of the host application is released, releasing a new version of the adapter for the object that factors in the impact of the exposed object, the adapter for executing in the same application domain as the managed code, wherein the adapter and proxy are instantiated within the application domain of the managed code.
2 Assignments
0 Petitions
Accused Products
Abstract
A method and architecture for increasing version resiliency between a host application that is unmanaged code and managed code is provided. A version resiliency technique specifies that the host application and the managed code communicate via an adapter that implements a protocol to access an object exposed by the host application. The version resiliency technique specifies that when a new version of the host application that impacts an interface exposed by the object of the host application is released, a new version of the adapter that executes within the application domain of the custom code is released. A version of managed code that adheres to the protocol will correctly interact with new versions of the host application that include a new version of the object because a new implementation of the adapter is also provided.
23 Citations
19 Claims
-
1. A method for providing version resiliency between a host application that is unmanaged code and managed code, the host application and the managed code communicating via an adapter and a proxy that implement a protocol, by a method comprising:
when a new version of the host application that impacts an interface exposed by an object of the host application is released, releasing a new version of the adapter for the object that factors in the impact of the exposed object, the adapter for executing in the same application domain as the managed code, wherein the adapter and proxy are instantiated within the application domain of the managed code. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
8. An architecture for exposing functionality of objects of a host application executing as unmanaged code to custom code executing as managed code, comprising:
-
an instance of an object of the host application within an application domain of the host application, the object providing an interface that is exposed to custom code; an instance of an adapter for the object within an application domain of the custom code, the adapter for communicating with the exposed interface of the object; and an instance of a proxy for the object within the application domain of the custom code, the proxy for communicating with the adapter via a protocol implemented by the adapter, the proxy for providing to the custom code an interface to the object, wherein when a new version of the host application is released with the object providing new functionality that is not available via the existing protocol of the adapter, releasing a new adapter that exposes the new functionality via a new protocol. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A method for providing version resiliency among a host application, a custom code runtime, and custom code, the host application being unmanaged code and the custom code being managed code, the host application and the custom code runtime communicating via an adapter that implements a protocol that is exposed to a proxy of the custom code, the host application, the custom code runtime, and the custom code executing in separate application domains, by a method comprising:
when a new version of the host application that impacts an interface exposed by an object of the host application is released, releasing a new version of a custom code runtime that provides an adapter for the object that factors in the impact of the exposed object, the adapter for executing as managed code within an application domain of the custom code runtime that is separate from the application domain of the host application and the application domain of the custom code so that when a version of the host application is released that impacts the interface exposed by the object, custom code can be developed to interact with the impacted interface via the adapter of the custom code runtime. - View Dependent Claims (15, 16, 17, 18, 19)
Specification