UpperSetting.OpenServer.Shared 1.0.0.37

Upper Setting's DotNetOpenServer SDK is our open source TCP client/server communication library that is lightweight, fast, secure and fully extendable enabling developers to quickly create native applications for any smart mobile device or desktop computer. Why? 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. How does it work? DotNetOpenServer implements a fast stateful binary protocol stack that supports SSL/TLS 1.2, includes a Windows Authentication Protocol, enables developers to extend the framework with any authentication method and provides a robust connection through a Keep-Alive Protocol (AKA Heartbeat Protocol). For more information and Android/Java and iPhone/iPad/iOS and Mac/OSX Objective-C APIs goto: http://www.UpperSetting.com

The Hello Protocol is included in the DotNetOpenServer SDK to show you how to create a simple application layer protocol. The Shared assembly contains a single abstract base class, HelloProtocol, that contains the unique protocol identifier and a log message function. The Server assembly contains a single class, HelloProtocolServer, that extends the base class. The class contains a single function to return a message back to the caller. The Client assembly contains a single class, HelloProtocolClient, that contains functions to synchrounsly and asyncronously send Hello command packets to the server. For more information and Android/Java and iPhone/iPad/iOS and Mac/OSX Objective-C APIs goto: http://www.UpperSetting.com

The Windows Authentication Protocol is included in the DotNetOpenServer SDK to provide server-side access control using Windows user accounts and groups. The Shared assembly contains an abstract base class, WinAuthProtocol, that contains the unique protocol identifier and common functions. The Shared assembly also includes an enumeration, WinAuthProtocolCommands, that contains the available protocol commands. The Server assembly contains a class, WinAuthProtocolServer, that extends the WinAuthProtocol base class. This class implements the server-side functions. The Server assembly also includes a class, WinAuthProtocolConfigurationServer, that contains the list of users and groups that are allowed to access the server. The Client assembly contains a single class, WinAuthProtocolClient, that extends the WinAuthProtocol base class. This class implements the client-side functions. For more information goto: http://www.UpperSetting.com

Upper Setting's DotNetOpenServer SDK is our open source TCP client/server communication library that is lightweight, fast, secure and fully extendable enabling developers to quickly create native applications for any smart mobile device or desktop computer. Why? 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. How does it work? DotNetOpenServer implements a fast stateful binary protocol stack that supports SSL/TLS 1.2, includes a Windows Authentication Protocol, enables developers to extend the framework with any authentication method and provides a robust connection through a Keep-Alive Protocol (AKA Heartbeat Protocol). For more information and Android/Java and iPhone/iPad/iOS and Mac/OSX Objective-C APIs goto: http://www.UpperSetting.com

The Keep-Alive Protocol is included in the DotNetOpenServer SDK to maintain and test connectivity between the server and client applications. The assembly contains a single class, KeepAliveProtocol, that implements the protocol within Windows Server, Windows Client and Windows Mobile applications. The assembly also includes an enumeration, KeepAliveProtocolCommands, that contains the available protocol commands. To use this protocol, simply call Initialize. Once initialized the protocol will automatically send Keep-Alive command packets to the remote end point. For more information and Android/Java and iPhone/iPad/iOS and Mac/OSX Objective-C APIs goto: http://www.UpperSetting.com