Ease of use
The framework is integrated with Visual Studio. Dragging the components
from the toolbox will create an advanced bidirectional communication system. The
actual code typing will be less than 8 lines of code.(see samples). No other setting
is required (like complex XML files) The framework takes care of everything, including
threading and interaction with GUI.
Object Based Communication
Any serializable object can be sent across the network (not just byte array
or string)
Duplex (bidirectional)
The framework can send the object from the client to the server and from
the server to the client without any limitation.
Firewall transparency
Unlike standard Remoting that can not communicate bidirectionaly behind
the firewall (proxy, NAT), DNR easily establishes the connection behind a firewall.
Broadcasting
The server can broadcast the message (the object) . Another option is UDP (object
based) Broadcast. UDP protocol allows for the transmission without specifying the
destination address.
Performance
The framework is faster than web services by 20 times on average.
With the use (optional)of the Serialization Studio, the performance may be improved even further. The framework
allows for sending the signature in the real time from PDA to PC (see RemoteDrawing
sample)
Cross Device Communication
The framework is built for the full and Compact Framework. It can transfer
the objects (classes, not just the strings) across the network from (to) different
devices and platforms. Communication with mobile devices (sample MobileClient)
Cross Platform Communication
The programs on different platforms can also communicate via DNRPlus. It is possible
due to the built in generic serializer that formats the objects uniformly on different
platforms (Windows, WindowsCE, WindowsMobile, Unix, Linux)
Keep Connection Alive
The framework allows for keeping the connection alive. It sends the special object
for that. If the object does not arrive on time, the event reconnection_request
is raised. Autoreconnection If this option is selected, the client will attempt
to reconnect. This option is very useful on Mobile devices when it switches to the
sleep mode for saving the battery. On wake up the client reconnects to the server.
GPRS
The framework can communicate using GPRS channel. (using GPRSconnector component)
Encryption
The data transferred (inc mobile devices) can be encrypted by the default encryptor.
If the user wants custom encryption, it can be also included in the framework.
DataSet Transfer
DataSet has native support in the framework. Fast serialization technique
is used for the dataset transfer.
Remoting/Sync/Async
All three methods can be chosen by the programmers to suite their needs.
Remoting is implemented in the same manner as a standard remoting. It executes the
methods on the proxy. Sync sends the object and waits for the reponse. Async sends
the object asynchronously.
Chunked file transfer with a progress
This feature is implemented for the large files that require a progress
indicator.
Chat components
ChatServer and ChatClient controls
indicator.
supports Socks4 and Sock5 proxies
HTTP or TCP/IP ?
The programmer can select the protocol selecting the component. (HttpSyncClient
or SyncClient) [same with a server]
100% managed Code
DotNetRemoting Online presentation
