Domäne
Desktop Development
Skill-Profil
IPC: named pipes, shared memory, sockets, D-Bus, Windows messages
Rollen
3
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
11
die anderen 4 optional
Desktop Development
Desktop Patterns
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (.NET WPF/WinUI/MAUI) | Understands IPC in .NET: Named Pipes (System.IO.Pipes), Memory-Mapped Files. Implements simple communication through NamedPipeServerStream/NamedPipeClientStream. Uses Process for launching child processes. | |
| Desktop Developer (Electron/Tauri) | Pflicht | Understands Electron IPC: ipcMain/ipcRenderer through contextBridge. Implements simple invoke/handle patterns. Uses preload scripts for secure IPC. Passes structured data between processes. |
| Desktop Developer (Qt/C++) | Understands IPC mechanisms in Qt: QLocalSocket/QLocalServer, QSharedMemory. Implements simple inter-process communication through named pipes. Uses QProcess to launch child processes. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (.NET WPF/WinUI/MAUI) | Develops IPC through gRPC (Grpc.Net) for structured communication. Uses Memory-Mapped Files for shared data. Implements single-instance through Mutex. Applies SignalR for local real-time communication. | |
| Desktop Developer (Electron/Tauri) | Pflicht | Develops typed IPC through TypeScript interfaces. Implements streaming through MessagePort. Uses SharedArrayBuffer for high-performance data sharing. Manages multiple BrowserWindows through IPC. |
| Desktop Developer (Qt/C++) | Develops IPC through D-Bus (QtDBus) on Linux and COM/Named Pipes on Windows. Uses QSharedMemory for shared data. Implements single-instance application through QLockFile and QLocalServer. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (.NET WPF/WinUI/MAUI) | Pflicht | Designs IPC architecture with .NET Remoting alternatives (gRPC, protobuf). Implements pub/sub through Message Queue. Optimizes IPC latency through Span<T> and zero-copy. Works with COM interop for legacy integration. |
| Desktop Developer (Electron/Tauri) | Pflicht | Designs IPC architecture with RPC-style layer. Implements pub/sub through custom event bus. Optimizes serialization through structured clone. Works with UtilityProcess for compute-intensive tasks. |
| Desktop Developer (Qt/C++) | Pflicht | Designs IPC architecture with Qt Remote Objects for multi-process applications. Implements synchronization protocols through shared memory, optimizes latency. Works with gRPC for cross-language IPC. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (.NET WPF/WinUI/MAUI) | Pflicht | Defines IPC strategy for .NET desktop platform. Establishes protocol standards, coordinates compatibility between .NET and native components through P/Invoke. |
| Desktop Developer (Electron/Tauri) | Pflicht | Defines IPC strategy for the Electron platform. Establishes IPC patterns and security guidelines. Coordinates cross-process architecture. |
| Desktop Developer (Qt/C++) | Pflicht | Defines inter-process communication strategy for the desktop platform. Establishes IPC protocol standards, coordinates cross-platform IPC compatibility. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (.NET WPF/WinUI/MAUI) | Pflicht | Shapes enterprise IPC standards for .NET desktop. Designs scalable IPC infrastructure. Evaluates new approaches (.NET Channels, StreamJsonRpc). |
| Desktop Developer (Electron/Tauri) | Pflicht | Shapes enterprise IPC standards for Electron. Evaluates new IPC approaches (UtilityProcess, WebWorkers). Designs scalable IPC architecture. |
| Desktop Developer (Qt/C++) | Pflicht | Shapes enterprise IPC standards for the desktop ecosystem. Designs scalable IPC infrastructure for multi-process architecture. Evaluates new approaches (io_uring, Windows copresence). |