Press Release Summary = .Net Communication framework for PC and PDA allows to build advanced network app
Press Release Body = DotNetRemoting communication framework for .Net Unlike standard .Net Remoting, DotNetRemoting SDK for .NET allows you to build Bidirectional network applications.
Features *Bidirectional synchronous and [or] asynchronous communication by sending the objects or executing methods on the server [or/and on client] *Built for .Net full and Compact Frameworks *DNR is the only available bidirectional framework for the Handhelds [PDA, PocketPC, Smartphones] *Outstanding performance [with DotNetRemoting Fast Serializer] *Accessibility for Clients behind Firewall or Proxy (Socks4 or Socks5 compatible, HTTP Proxy ) *Supported protocols TCP, HTTP, UDP *HTTP and TCP Object based Broadcasting *UDP Object based broadcasting *File Transfer *Encryption *Easy deployment [coping] *No deployment license fees *100% native .NET code *GPRS support *C# and VBNet sample code included *New major components: HttpClient, RawClient, RawServer, HttpProxyServer, HttpProxyClient.
DotNetRemoting framework does not rely upon the events (or callbacks). It creates bidirectional channel on the top of the socket. All the classes in the hierarchy are derived from the base class that holds the socket. This approach makes the asynchronous call as the most appropriate, also It allows to make the communication behind the firewall possible. The port has to be opened on the firewall. If your NAT or firewall supports socks 4(5) protocol, You may connect your client through ProxyConnector component. You need DotNetRemoting if *You need a quick solution and you do not want to spend your time on connections, activations, threads synchronization and firewall transparency. The framework takes care of everything *You want bidirectional communication. *If need a top performance. *Communication with mobile devices (Pocket PC, smartphones) *You need GPRS comms channel on your PDA *Encryption *Firewall transparency *Easy deployment Synchronous vs. Asynchronous Calling the methods in standard .Net remoting is always synchronous process by definition. In other words you always have to wait for the completeion of the call. That is how any standard call of any method works. It is good for short operations, but what if the operation is lengthy? What if the server is doing intensive and lengthy database search? Your application is frozen until the call returns. DNR supports two models at once - synchronous and asynchronous. You can use RMI/RPC for synchronous calls - like in traditional .Net remoting. Or you can use asynchronous When the response comes, it invokes method on your class and most importantly it invokes it in the main thread. Why is it so crucial that it invokes the method in the main thread? It is essential because any attempt to invoke GUI method from the worker (not main) thread at best will crash your application, at worst the behavior of your application will become unpredictable.
Web Site = http://DotNetRemoting.com
Contact Details = Address: 3/198 Ferntree Rd., Gosford Australia
2009
