Bulk API for Registrations

[andrewbonney]

The need to register each Node/Device/Sender/Receiver etc sequentially via the Registration API creates a bottleneck and delay when large devices first start up. A bulk method has been requested as an addition to the Registration API which would allow more resources to be registered in a single request payload.

When developing such an addition, it is suggested that the bulk API in IS-05 is used as a point of reference in order to keep behaviour as common as possible between the APIs.

Care must also be taken when registering resources which relate directly to each other. For example, via the 'single' API a 'Device' cannot be registered until its corresponding 'Node' has been registered. Consideration should be given to whether a bulk API should be restricted to registering a single type of resource at any one time (Node/Device etc), or if multiple types are permitted in a single request how the server should handle this to ensure referential integrity.

[VenkateswaranJ]

Any update on this? It's really painful when we have a node with several 100 subresources.

[garethsb]

I suggest you bring your quantitative findings to the AMWA Incubator, identifying where the pain comes from. You may get help to improve things within the scope of the current spec, or support from other AMWA members to bring an activity proposal to explore bulk registration.