Developer Resources:

Customer Quotes:

Remoting Services Types

WebORB enables remoting for .NET Remote Objects and 3rd party XML Web Services. This means Flex, Flash, AJAX and Silverlight client applications can use the same APIs to communicate with web services as they would with plain .NET objects.

Simple Deployment Model

Turning .NET objects and XML Web Services into remoting services for Flash, Flex, Silverlight and AJAX access is very straight-forward. To expose a .NET class as a remoting service, simply copy the assembly with the target class into the /bin folder of a WebORB-enabled virtual directory. Once the assembly is copied, you can see the classes in the WebORB service browser.

Secure Access

.NET classes deployed into a WebORB-enabled virtual directory can be easily secured to prevent unauthorized access. WebORB offers multiple security mechanisms, including graphical security configuration, support for .NET roles-based security, pluggable authentication and authorization handling and finally support for open and closed security modes.

Client/Server Type Mappings

WebORB implements a very robust type mapping system to establish smooth flow of data between different rich client technologies and .NET.  For instance, serialization of the ADO.NET types like DataSet and DataTable automatically converts them to a collection of objects recognized in the client system - ActionScript objects for Flash/Flex clients, JavaScript for AJAX clients and .NET complex types for the Silverlight clients.  Method arguments and return values can be .NET generics, standard collections, .NET GUID objects, NHibernate proxies, primitives or user-defined classes.