Michal Princ

Hello @infn-ke , correct, the size of to-be-sent message is checked and RL_ERR_BUFF_SIZE is returned once exceeds the RL_BUFFER_PAYLOAD_SIZE. However, the fragmentation support is not planned, this is up to...

Hi @SASIDHARAN-dot , thank you for this notice. You are right that kErpcStatus_Timeout is never returned. This piece of code has been integrated within the #121 PR. @pgu-swir , was...

Thank you, @pgu-swir , understand the motivation. Not necessarily the erpc recovery is needed each time an error is returned from the transport layer. What about to introduce the kErpcStatus_FatalError...

@Hadatko , may I ask for your opinion? (1) would you use _Timeout or _FatalError for a non-destructive error from the transport layer? (2) Should we unblock all pending clients...

Hi @saimukund, please take a look to #174

Hello @saimukund , I think we have to focus on the correct behavior of the TCP transport layer and the erpc infrastructure first, instead of trying to workaround it by...

Hello @ramlco , supporting multiple clients and providing such examples is on the todo list but due to other work priorities this is not going to be done soon, unfortunately.

Hi @Peanut0709 , could you be more specific, please? Thanks.

> > > It looks like files like test.py, run_test.sh are obsolite or not all files were published. If they are obsolite also README in same folder should be updated...

Hello @drumairali I am afraid we do not have such an example (combining Python on one side and the C on the other side) in the eRPC repo. BUT, there...