locka99

Yes I agree. I think until async permeates through the api it would be the only way to do it.

Probably the best way to start is to look at new_sample() in builder.rs since that produces a working sample server config and demonstrates how to programmatically create one. You can...

Hi, I agree the client API is a little confusing. The current default behaviour for the client is that you define the endpoints you expect to be on the server,...

One further improvement is could probably do this (again pseudo code) ``` let mut client = ClientBuilder::new().client.unwrap(); let endpoints = client.get_server_endpoints_from_url(server_url); //.... ``` i.e. you don't need to supply an...

No probs & enjoy your holidays! When you're back, let me have a sample of what you're doing and I will see if I can identify where the issue lies.

I haven't commented yet but when it comes to async, are you wanting async in the futures / tokio sense where you have async / await style functionality, or async...

Thanks I think this should be easy enough to fix although I haven't tested with IPv6 so I don't know if there are issues to be found with that form...

Subscriptions are managed by a state table which dictates how long they are kept alive for depending on there being pending notifications, publish requests etc. It is very complex, especially...

For reference, arrays are encoded like so: https://reference.opcfoundation.org/v104/Core/docs/Part6/5.2.5/ Inside variants, arrays may be single or multi-dimensional and the encoding dictates what the variant holds: https://reference.opcfoundation.org/v104/Core/docs/Part6/5.2.2/#Table15 As far as I am...

Ignore last commit comment, I referenced the wrong bug