Re: [milo-dev] Library maturity and stability

[Kevin Herron <kevinherron@xxxxxxxxx>]

There is currently a big ease-of-use addition to the client SDK being developed in the dev/0.5 branch. It will change the UaNode and AddressSpace APIs but not the core OpcUaClient and subscription-related APIs.

That said, aside from potential API instability, the implementation itself is mature. It's being used by a number of large companies in thousands of customer sites.

The new, easier to use subscription APIs have already been merged into dev/0.5 and the refactor of the UaNode and AddressSpace stuff is happening in https://github.com/eclipse/milo/tree/0.5-client-nodes-and-address-space. I'd be happy to answer any questions you have about these.

I had hoped to reach version 1.0 by September this year. Covid has knocked things off track a little bit, but it may still be possible.

On Fri, Jul 3, 2020 at 8:31 AM Paul Vorbach <paul.vorbach@xxxxxxxxxxxxxxxxxx> wrote:

Hello,

I'm considering using this library for a new project and I'd like to ask if the milo client SDK is ready for production use in its current state.

Are there any plans for major refactorings right now or in the foreseeable future or is the API considered stable as it is?

I'm asking this because milo is still in a 0.x version and I'd like to plan for additional effort that will be required in the near future.

Kind regards,

Paul

_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/milo-dev