Upper Setting's DotNetOpenServer SDK is our open source communication library that is not only lightweight, lightning fast and secure but also fully extendable enabling developers to quickly create native applications for any smart mobile device or desktop computer.
Unlike most application server frameworks, which are implemented over slow stateless protocols such as HTTP, REST and SOAP that use bulky ASCII data formats such as JSON and XML, DotNetOpenServer has been built from the ground up for speed and efficiency.
|DotNetOpenServer SDK||DotNetCloudServer SDK|
|Android, iOS, Windows Phone, Windows, Mac and Java APIs|
|Persistent stateful connections|
|Interface driven authentication protocol layer|
|Built-in support for Windows Authentication|
|Robust 2-way keep-alive/heartbeat protocol|
|Simple API to create application layer protocols|
|Remote Object Access Protocol|
|Remotely invoke methods, subscribe to variables and receive events|
|Granular read/write/execute authorization for methods, variables and events|
|Redistributable license model|
How does it work?
DotNetOpenServer implements our own open source fast stateful binary protocol stack we call FASTack, short for Fast Access Stack. So what makes FASTack secure and robust?
Both the client and server APIs leverage pre-exising components offered by each operating system enabling support for SSL/TLS 1.2.
Session Layer Protocol
Our session layer protocol has been designed to minimize the amount of damage denial of service (DOS) attacks can impose yet supports large packets.
Authentication Protocol (AUTHP)
We have implemented an Authentication Protocol (AUTHP) layer that is fully extendable. Out of the box, DotNetOpenServer supports Windows Authentication, however; any authentication method can be implemented by simply extending our simple base authentication class.
Keep-Alive Protocol (KAP)
A common problem many stateful client/server applications encounter is the ability to expose network failures in a timely fashion. DotNetOpenServer solves this problem with our Keep-Alive Protocol (KAP) commonly referred to as a heartbeat protocol. Both the client and server send tiny packets back and forth. As soon as the heartbeat stops the framework notifies the application the network has failed enabling server-side component objects to release associated resources and notifies the end user a network failure has occurred.