Lines Matching full:resource

25 LwM2M uses a simple resource model with the core set of objects and resources
48 *Resource definitions*
223 The server could query the ``Manufacturer`` resource for ``Device`` object
227 The full list of registered objects and resource IDs can be found in the
260 Create callback functions for LwM2M resource executions:
337 Next we assign ``Security`` resource values to let the client know where and how
358 	 * Manufacturer resource of Device object = 3/0/0
368 	/* Reboot resource of Device object = 3/0/4 */
394   Security Mode (Resource ID 2) set to zero (Pre-Shared Key mode).
395   Identity (Resource ID 3) contains PSK ID in binary form.
396   Secret key (Resource ID 5) contains the PSK key in binary form.
402 …Server Public Key resource (ID 4) must contain a server certificate or CA certificate used to sign…
407   When no security is used, set Security Mode (Resource ID 2) to ``3`` (NoSec).
409 In all modes, Server URI resource (ID 0) must contain the full URI for the target server.
469 Writing a value to a resource can be done using functions like lwm2m_set_u8. When writing
490 When data cache is enabled for a resource, each write will create a timestamped entry in a cache,
492 resource.
496 Supported resource types:
507 enable the cache by calling :c:func:`lwm2m_engine_enable_cache` for a given resource. Each resource
508 must be enabled separately and each resource needs their own storage.
532 internally reads the content of a given resource. This has a side effect that any read callbacks
533 registered for a that resource are ignored when cache is enabled.
746             Execute a resource
749             Read value from LwM2M resource
759             Write into LwM2M resource
768             Create object or resource instance
771             Delete object or resource instance
774             Enable data cache for resource