.NET Remoting

Abstract: Component Object Model (COM) and Distributed Component Object Model (DCOM) provide the foundation for Microsoft's distributed object strategy. They are the glue that should enable Microsoft to bring their other core products and technologies such as ActiveX, Internet Information Server, and Internet Explorer to the enterprise. In other words, this is Microsoft's answer to CORBA, Netscape, and JavaBeans. This text discusses: how to use COM and DCOM with existing legacy systems; how COM and DCOM fit into two- and three-tier client/server architectures; "Thin" versus "Thick Clients" and how they relate to Microsoft's Active Server Platform; new technologies from Microsoft such as Viper and Falcon; and security issues for distributed objects.

Abstract: Systems and methods for providing a media device capabilities determination mechanism in a networked computing environment are provided. Some of today's operating systems and applications deliver a set of remoting features to enable a networked ecosystem of remote media consumption devices. These devices connect to the host and display a remoted media experience via remoting protocols and technologies. In this regard, the device capabilities determination mechanism of the invention enables a remote device to specify a custom set of media capabilities that should be remoted from the host to the remote device.

Abstract: Methods and systems for transparent user interface integration between remote (“published”) applications and their local counterparts are described, providing a seamless, unified user experience, and allowing integration of a start menu, dock, taskbar, desktop shortcuts, windows, window and application switching, system tray elements, client-to-host and host-to-client file type association, URL redirection, browser cookie redirection, token redirection, status message interception and redirection, and other elements. These methods and systems further enhance theme-integration between a client and remote desktop or virtual machine by remoting all UI elements to a recipient for generation, including text controls, buttons, progress bars, radio buttons, list boxes, or other elements; presenting them with the receiver's product and OS-specific UI; and returning status back to the sender. This may achieve a more unified and transparent UI integration. Furthermore, international text may be correctly received in cross-language environments, or translated into the language of the presenting environment.

Abstract: A system providing improved methods for remote method invocation of a service is described. The system includes methodology for a client to cast, at design time, a generic interface class to a remote service having a defined interface. The generic interface class dynamically generates a proxy for making a remote method call on the remote service at runtime, while also providing for runtime type checking. Moreover, the generic interface class is subclassed to provide support for particular wire formats and methods of transport. The dynamically generated proxy converts a remote method call by the client into a wire format specified in the remote service's interface definition and calls the remote service using the method of transport specified in the interface definition. The system also includes methods to support making a service available to remote clients. The system includes modules that listen for remote method calls on a service and deserialize these calls into native format. This enables the service to be invoked by a native call in native format. The method includes reserializing results of the native call and returning these results in response to the remote method call.