Generate client libraries / SDKs

[narve]

This, as with issue #20 , is an optional task to set up a task to automatically generate client libraries in one or more languages.

Generating client libraries will make it easier for market participants to integrate with FMOs, and increase the compatibility between different FMOs / different implementations of UMEI.

[narve]

For NODES, our partners are using DotNet and Python, so generating client SDKs for these languages are enough. How about @cdmNSIDE ?

[cdmNSIDE]

Hello Narve,

I agree that what you propose is something useful for a large diffusion of the UMEI and to facilitate the integration of the tools of the customers with the UMEI.
Nevertheless, I think it's not the priority to go in that direction for the UMEI.
Indeed, we don't have yet any information on the programming languages that will be used by the market participants. I would not implement the client libraries in all languages proactively since it would require an important maintenance cost and knowledge in all those languages.
I would wait to see if the standard proposed (HTTP communication) is sufficient or not for the market participants.

[narve]

It is certainly not a priority. But if we are asking partners to integrate with UMEI, and we're implementing UMEI ourselves, it could be useful to avoid duplicated work.

I propose that we close this issue, but keep in mind that we might save some effort (and increase consistency) when we actually start implementing the standard.

[narve]

FYI: I have created code to generate client and server stubs for UMEI when integrating it with our existing solution. Let me know if you are interested in a demo/walkthrough.