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]

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.

[Michal Mühlpachr]

Well it would be nice to allow SLM general use and fix AT commands that way that any response received can be identified with 100% certainty weather bytes/characters are from SLM or from IP/UDP backend i.e. socket.
Why customization would be required for that especially if there no special reason why the URC is sent after the data instead of before it.
URC notification about data availability is needed either to be able to get INDICATE PIN notification while SLM is in #XSLEEP=2 - e.g. during eDRX cycle.
What do you think ?