add IPC workshop
This commit is contained in:
parent
bdfe4afd03
commit
35f9095aaa
@ -67,6 +67,13 @@ This chapter will introduce the object manager and expand the knowledge of the t
|
||||
by showing how to conveniently create global addressable objects. The chapter description and
|
||||
solutions are located inside [`ws-objects`](https://egit.irs.uni-stuttgart.de/fsfw/fsfw-from-zero/src/branch/main/ws-objects).
|
||||
|
||||
## WIP: IPC workshop
|
||||
|
||||
Usually, objects have to interact with other objects or software internal entities like
|
||||
threads of OS services in some shape or form. This workshop introduced methods to perform
|
||||
this Inter-Process communication (IPC) in a thread-safe way. The chapter description
|
||||
and solutions are located inside [`ws-ipc`]()
|
||||
|
||||
## WIP: TMTC workshop
|
||||
|
||||
Provides an introduction into TMTC handling, as virtually all space systems are remote systems
|
||||
|
0
ws-ipc/README.md
Normal file
0
ws-ipc/README.md
Normal file
@ -139,7 +139,7 @@ of the object, you can also add units to schedule by using their object ID.
|
||||
Please note that the object manager is a software entity which global mutable state. This
|
||||
is something which can easily introduce subtle and dangerous bugs into a multi-threaded
|
||||
software. If you are sharing an object with the manager between multiple threads, all object
|
||||
access needs to be protected explicitely with concurrency tools like a Mutex by the developer.
|
||||
accesses needs to be protected explicitely with concurrency tools like a Mutex by the developer.
|
||||
|
||||
The object manager has no own capabilities to ensure thread-safey in such a case.
|
||||
It is recommended to do the `ws-ipc` workshop to get familiar with various ways for objects
|
||||
|
Loading…
Reference in New Issue
Block a user