silber-1.1

Added several enhancements as an increment over silber-1.0:

1 Added usage of an isolated memory block for each client for Responses. The library doesn`t validate client ID, which is the server's responsibility.
2 Improved getting a response with no additional copy. The client can operate with reserved memory until the next request is sent.
3 Added the possibility of installing the library and headers. It can be useful for developers, where such library can be linked for multiple targets(applications).
4. Add a non-blocking call for awaiting server readiness. Users can specify how long it may wait if server is not ready. For real-time computing, operations can be used to handle outdated requests. (polling period 5ms)

Full Changelog: 1.0...1.1

silber-1.0

Lightweight implementation of messaging between processes or threads.

1. Implement Client and Server messaging roles. Declarative principle: Client requesting and getting a response. The Server is waiting for requests and answers based on the application's business logic.
2. Implement one-to-one ( Server <-> Client) messaging.
3. Implement one-to-many (Server <-> Client_1 , Client_2, Client_3 ... Client_N ) messaging.
4. For getting a response from the Server, Client allocates the needed response type. The response will be fulfilled if the message type is expected.
5. Message Flow must be agreed upon as an imperative part of Client vs Server communication.
6. The Server can process only one request per time. During this time other requests will be waiting and blocked.
7. Added test application to show: 'one-to-one' and 'one-to-many' types of messaging.

Supported platforms:
Linux, Windows, Mac OS.

What's Changed

New Contributors

• @MaksymT17 made their first contribution in #1

Full Changelog: https://github.com/MaksymT17/silber/commits/1.0