Hi All,
I am working on genivi dlt-daemon project.As per existing code, IPC mechanism is implemented using FIFO and UNIX_SOCKETS between DLT user application and DLT-daemon
I have the below queries regarding IPC procedures used in DLT tool
1.why FIFO and UNIX_SOCKETS are preferred over message queue/shared memory in DLT-Daemon Application-Design point of view. Anyone of you know the exact reasons behind it. if yes, could you please explain those in terms of use-case(s)?2.what are limitations/drawbacks of FIFO and UNIX_SOCKETS in DLT-daemon application perspective and is there any planned actions to improve such limitations in future releases?3.when we should enable FIFO instead of UNIX_SOCKETS in DLT framework to get better throughput and vice versa?
Thanks,Yaduvanshi Satish
Hi All,
I am working on genivi dlt-daemon project.As per existing code, IPC mechanism is implemented using FIFO and UNIX_SOCKETS between DLT user application and DLT-daemon
I have the below queries regarding IPC procedures used in DLT tool
1.why FIFO and UNIX_SOCKETS are preferred over message queue/shared memory in DLT-Daemon Application-Design point of view. Anyone of you know the exact reasons behind it. if yes, could you please explain those in terms of use-case(s)?2.what are limitations/drawbacks of FIFO and UNIX_SOCKETS in DLT-daemon application perspective and is there any planned actions to improve such limitations in future releases?3.when we should enable FIFO instead of UNIX_SOCKETS in DLT framework to get better throughput and vice versa?
Thanks,Yaduvanshi Satish