SLM UDP arbitrary received data size by #XRECV and #XRECVFROM

[Michal Mühlpachr]

Hi,

I do not know how to reliably get size of arbitrary UDP data received by #XRECV or #XRECVFROM.

It is clear for text data, but for binary data both #XRECV and #XRECVFROM do not report size of received data in advance before data.

Because arbitrary binary data can contain <CR><LF> or even "#XRECV: <any number>", how size of received data reported by SLM can be distinguished reliably?

Why #XRECV and #XRECVFROM do not report size of received data BEFORE data (that would work fine)?

Thank you.

Regads,
Michal

[helsing]

Hi Rick,

Justl letting you know we are now back from Easter vacation. I will look into this and get back to you.

Best regards,

Håkon

[Michal Mühlpachr]

Is there any update on this issue (answer ETA) please ?

[helsing]

Hi Michal,

I am checking with the developers. I am not sure exactly when we will hear back, however, likely before the end of the week.

[Jun Qing ZOU]

Hi Michal, beside data length the URC also serves as "end of data" indication.

[helsing]

There is no special reason why the URC is sent after the data instead of before it. It is possible for you to make the change as a customization.