| Re: [wakaama-dev] LWM2M Discover request not handled by client |
|
Hi Sorin, Sorry for the delay. There were a lot of vacations these last two weeks in Europe. Regards, David Navarro From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sorin Zamfir Hi all, I haven't received any feedback about this ... and I'm beginning to think this mail was never received or was never approved Best regards, Sorin From: Sorin Zamfir <zamfir.sorin@xxxxxxxxx> Hi guys, While testing some custom object scenarios i've observed that triggering a Discovery request from a LWM2M server to the wakaama client on a specific object
or even client endpoint doesn't reply with actual object links as it supposed to as by the LWM2M standard section 5.3.2. Instead the request is treated as normal object read and as far as i can see from the management.c there is no handling for such a request. (as stated
by LWM2M standard section 8.2.4 in the table operation to method mapping) To be more specific i somehow expected the client to handle such a discovery request as follows : GET Accept : application/link-format URI <----- request 2.05 Content-Format : application/link-format ; Payload : </objectId> , </objectId/instance0/0> , </objectId/instance1/0> <---- response I find this scenario to be quite critical when instances can be dynamically managed by the client (created or deleted). Without this , even though registration
updates are performed periodically the cached resource URIs on the lwm2m backend are never brought up to date unless the client is restarted.
Cheers, Sorin
--------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for |