Introducing ConnectSMB

History

There's a bit of history to ConnectSMB. Prior to ConnectSMB, the smb stack was marketed as ConnectedNAS and ConnectedSMB. These products were less module with less flexible configuration than ConnectSMB. Before that, there was the Blue Share CIFS Product. This product only supported an SMBv2/SMBv2 client.

Purpose

As a framework, it provides a portable platform independent abstraction for Windows, MacOS, Linux, Android, and select RTOSes.
It provides a sophisticated real-time, asynchronous programming model. Non-blocking, state-driven applications can be easily deployed.

As an SMB stack, ConnectSMB is a SMBv2/SMBv3 Client/Server stack supporting Active Directory and NTLM authentication, Distributed File System, security, and many other features.

APIs

ConnectSMB provides it's own C runtime, thread/process abstraction, time of day, XML, extensible persistence and configuration, sockets and networking, file handling and multiple plugin file handlers, buffer management, locks, plugin heap managers, real-time event scheduling, and much more.

Asynchronous Real-Time Event-Driven

ConnectSMB async scheduling is based on the notion of single run loop implemented as a platform thread. All scheduling occurs within the run loop. There can be multiple run loops and those run loops can be assigned to individual cores for a robust SMP solution.

Multi-Platform

ConnectSMB native platform is Linux but applications built with it implicitly supports all platforms. ConnectSMB is extensible so that new platforms, heaps, and file handlers, can easily be added.

Source Licenses

Our core framework is distributed under the Creative Commons, Attribution, No Derivitives License.

We want to contribute to the community but wish to avoid exploitation. We are flexible so if you wish to license it differently, just contact us via our contact page on our website

The SMB modules are distributed under a proprietary Connected Way License.