Basic questions on the API to ConfD

Core Engine and APIs
11

Thanks Wai.
I understand some of the motivation of not going with Stub based approach where the stub is generated.
That said - I have a feeling that one of the 2 approached will be used by the users:

  1. Manually coding all subscription options, iterating over replies with a full knowledge of the schema. When I iterate over a specific reply, I know what I’m looking for, child, siblings etc… But it means a special code is written to parse any reply. Maybe I’m missing here something and there can be a single iterate loop for virtually every single subscription.
  2. People will opt to an XML representation. I just discovered this: How to convert a ConfD tag value array to XML? . So I can generate an XML and pass it to something that can deserialize it or hand it over to something else that understand XML and can extract the values. But it’s slower than having it done directly with the C-API. Slower because it still string generation.