"BootstrapConfig" should be a list of request

[sbernard31]

Currently the bootstrap server is configurable by adding a bootstrapConfig for a given endpoint.

This bootstrap config is a list of Security objects and Server objects.
A bootstrap session will start by a Delete on / then a Write request for each Security objects then a Write request for each Server objects.
This is not so flexible.

The bootstrapConfig should rather be a list of requests (write,delete) to send.
This allow to :

• support all objects,
• do not force to start with delete "/" (delete only object you need to delete),
• do request in different order.

But this will not cover cases where we need to make complex processing (using discover, using previous result to guess what to send ... ... ), I don't know what this might look like.

[sbernard31]

After several thoughts and tries about making the BootstrapConfig more flexible we finally think this is maybe not a so good Idea.

We try to implement this in #883 and as explained at #883 (comment) this bring new issues ...
This makes make us feel there is no way to provide a kind of Bootstrap Config which could supports correctly all use-cases.

Those makes us think that maybe we should keep BootstrapConfig which aims to :

• be easy/straightforward to use for main use cases.
• but with limited feature.

In addition, the code should be refactored to make easier to integrate custom behavior and so support all cases.

This means that recent addition of #883 was probably a bad idea and will be removed/replaced by new classes.

[sbernard31]

#1027 is a new try to achieve those goals.

[sbernard31]

I think #1027 achieve this goal.
This new API will be available in Leshan v2.0.0 since M4.