DotNetRemotingPlusLib 1.0.3 Communication Framework F...
Core 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, Smartphone]
*Outstanding performance [with DotNetRemoting Fast Serialize]
*Accessibility for Clients behind Firewall or Proxy
*port socks proxy 4, 5 protocol
*Supported protocols TCP, HTTP, UDP
*HTTP and TCP Object based Broadcasting
*UDP Object based broadcasting
*Easy deployment [coping]
*No deployment license fees
*100% native . NET code
*C# and VBNet sample code included
*New major components: HttpClient, RawClient, RawServer, HttpProxyServer, HttpProxyClient.
*In HTTP mode the server may act as a gateway/proxy server. All the calls not addressed to DNRPlus server, are relayed to the HTTP server (IIS for example) That enables to run on the same port and the host a website (with webservices if required) and to have at the same time bidirectional communication with DNRPlus clients. The only condition is that the network must support HTTP 1. 1 protocol in order to keep the connection alive.
DotNetRemoting communication framework for . Net
*Accessibility for Clients behind Firewall or Proxy (Socks4 or Socks5 compatible, HTTP Proxy )
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
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.
What is new in official DotNetRemotingPlusLib 1.0.3 software version? - This suite is a new generation of network communication componets. Most of the functionality is inherited from DotNetRemotingLib3.0.5. What is expected in the future? Newly-made DotNetRemotingPlusLib 1.1 be downloaded from current page, we also looking forward to unconfirmed 1.2 release build. You may download go.php@sid=1 directly, estimated download time by ISDN or CDMA [~128 kbit/s] is 0:01:03. Just write the reviews of the DotNetRemotingPlusLib. System requirements are .Net framework. Program has been scanned and verified by the several antivirus and anti-spyware applications and DotNetRemotingPlusLib found to be clean. No guide or DotNetRemotingPlusLib tutorial available. The following languages are supported by DotNetRemotingPlusLib: English.