silber-1.0
Lightweight implementation of messaging between processes or threads.
- 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.
- Implement one-to-one ( Server <-> Client) messaging.
- Implement one-to-many (Server <-> Client_1 , Client_2, Client_3 ... Client_N ) messaging.
- For getting a response from the Server, Client allocates the needed response type. The response will be fulfilled if the message type is expected.
- Message Flow must be agreed upon as an imperative part of Client vs Server communication.
- The Server can process only one request per time. During this time other requests will be waiting and blocked.
- 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