This is the library that sits at the heart of qaul.net.
Fundamentally, it handles three types of interactions:
- Initialised hardware messaging
- Service messaging and service hosting
- Internal storage, parsing and encryption
The two things provided by libqaul, that make it useful to other
Qaul, the primary data struct and API holder,
plus the "service API" (implemented on
Qaul) which gives a
developer access to a qaul network.
The initilisation order for the libqaul stack is reverted.
- Hardware modules (
netmod) for the appropriate platform
RATMANrouting core, binding against available network interfaces
- (Optional) Platform specific storage shims for
Qaulinternals, which sets up storage, encryption and user stores
- API shims such as the
http-apiwhich exposes the service API on a json:api schema
- UI threads: either initialise the qaul.net web-frontend or your own application stack
libqaul handles user registration, sign-in and out, messaging,
file-sharing, both encrypted and public communication, voice
calls, as well as service hooks that mean that your applications
can communicate with the existing services, and other instances
running across a qaul network.
Additionally to providing the entire application stack,
can also tunnel to other
libqaul instances, depending on the
platform. This means that your application might be shipping an
entire copy of
libqaul, but doesn't have to be the network entry
point. This initialisation option is available before starting
libqaul api scopes
Contact books for users, storing the users they know about.
Error and Result handling
API fascade module?
Service API messaging primitives
A generic object identifier
Primary context structure for
A generic metadata tag