Asynchronous Cooperative Flows › Asynchronous Processing with CA Gen Proxies

Asynchronous Processing with CA Gen Proxies

Using the CA Gen proxies, a user-written client application can make asynchronous requests of a target server. The set of exposed proxy interfaces includes APIs that provide a user-written client application with the ability to communicate with a target DPS in an asynchronous fashion.

Similar to the action language described for generated client applications, asynchronous support for a proxy influences only the handling of a request's corresponding response. Initiating a request to a target DPS is no longer synchronously linked with obtaining its response. After a request is accepted for processing by the CA Gen Proxy Runtime, the client application is able to engage in other processing. The server processing proceeds asynchronously to the client processing. The client application is able to obtain (or ignore) a given outstanding response when it is best suited for the application logic.

CA Gen supports four types of proxies, as described in the following list:

• The ActiveX/COM Proxy is a generated COM object that provides an automation interface to CA Gen servers. Providing a COM automation interface lets web applications with Active Server Pages and any OLE-enabled client access to CA Gen servers.

  A set of common properties and methods supports Asynchronous behavior in the generated COM Proxy interface and the COM Proxy Runtime. A client application that wishes to take advantage of a given COM Proxy's asynchronous processing must invoke its exposed asynchronous interface method. For more information about generating and using an Active X/COM Proxy, see the Distributed Processing – Proxy User Guide.

• The Java Proxy is a Java-based interface that lets Java applets and Java applications access to CA Gen servers.

  A set of common properties and methods supports Asynchronous behavior in the generated Client Java Bean and Application Java Bean. An applet or application that wants to take advantage of the asynchronous processing ability of a Java Proxy must invoke the exposed asynchronous interface methods of the bean. For more information about generating and using a Java Proxy, see the Distributed Processing-Proxy User Guide.

• The .NET Proxy is a generated .NET object that provides an object-oriented interface to the CA Gen servers. The .NET Proxy and associated the CA Gen runtimes are 100 percent managed .NET code. Providing a .NET managed object interface lets any .NET aware application access to CA Gen servers. Typical user applications would be stand-alone programs (VB.NET or C#) and ASP.NET web applications.

  A set of common properties and methods supports Asynchronous behavior in the generated .NET object. A .NET aware application that wishes to take advantage of a given .NET Proxy's asynchronous processing, must invoke the respective object's exposed asynchronous interface methods. For more information about generating and using a .NET Proxy, see the Distributed Processing – Proxy User Guide.

• The C Proxy API is a generated C language header file that provides you with the flexibility to call CA Gen server components from a C language application, or applications that support a C language interface.

  The C Proxy Runtime contains a set of APIs that support asynchronous behavior. A client application wishing to use asynchronous processing must use the specific asynchronous function calls, as described in the Distributed Processing—Proxy User Guide.