Define custom objects when awa-serverd starts about awalwm2m HOT 2 CLOSED

The architecture is designed to support application-specific object definition through the use of the API or the Awa Tools. For example, a simple bash script could be used to define a set of IPSO objects, and this script can be run after the server has been started.

However we are considering adding support for custom objects to the client daemon startup, as there is currently no way to define objects in the client before it connects to the server, and it would be useful for the client to have the correct set of object definitions prior to registration, to help eliminate unnecessary server work when new definitions are added later.

It may be feasible to extend this client feature to the server once implemented.

from awalwm2m.

Version 0.2.0 should include support for "Object Definition Files", which are XML files that describe object/resource definitions. Both client and server daemon will support loading zero, one or more of these files at start-up, before any IPC or CoAP network traffic occurs. Default values for mandatory resources can be specified too, with the caveat that strings will need to be base64-encoded.

We intend to include an example/template for standard objects.

from awalwm2m.