2.6.0 Introducing Async and Sync messaging and interprocess lock
I am pleased to disclose a great additions to CorePartition:
-
Introducing Async Message Broker using Publish/Subscriber and topics to control async process intercommunications.
Now using topics a thread can subscribe to asynchronously receive data published from other threads. -
Introducing Sync Wait / Notify thread blocking procedures using Tags as the lock identifier and optionally capable to send messages
Now CorePartitionOS will provide InKernel Wait/Notify Locks, but the same channel can also be used to send interprocess messages, the destination will be identified with a Tag that resembles Topics but only defines sync messages. -
Introducing Message Payload, messages will be always identified (what thread generated that) and with a (32bits)Attribute and (64bitds)Value, sou a single topic or tag can do more than just sending a simple message, can send parameters and values (tuple) across the system.
Not only values will be sent, but attributes that will define what is it for, so, you can use a single TAG to do much more than jus receive data. -
Rewritten Scheduler to be adapt to the new functions.
The timer based scheduler was entirely rewritten to accommodate special states for interprocess communications -
Dropping full FreeRTOS support. It means it still can work, but we will no longer officially support it executing it as part of the RTOS solution, only of Computers OS's
-
The Full thread addressing inside the code was enhanced to make it faster and directly reference the actual thread.