Single user application limitation for IPC interface

[arjunprakash84]

Thank you! Awa LwM2M looks like one of the best LwM2M frameworks available right now.

The user guide states that "Currently the IPC interface is implemented as a simple UDP channel, with an associated UDP port. It is recommended that only a single user application connect to the daemon's IPC interface at any time. ". Can you please give some details on why this limitation exists?

Also, what is the current status of the Python APIs for IPC interface?

[DavidAntliff]

@arjunprakash84 the limitation exists as a recommendation because, apart from a Session ID, there are no integrity checks on either the client or server daemon to ensure that separate simultaneous applications do not cause each other problems. It hasn't been extended or tested simply due to it being what it is, currently. You may be able to make it work if you're careful. Improvements to IPC are on the roadmap I think.

There is a "hidden" Python API that is currently used only in the test framework for the tools. It provides some basic support and is intended to be the basis for a full API however I believe that is on the roadmap for future implementation. Patches/pull-requests are welcome, of course!