locka99

yes that looks like a bug. I don't know if it would cause a slow down because the publish requests get sent on a timer so the worst that would...

I can think of a few simple ways to fix this, depending on your needs: 1. Call write() service with more than one variable to write in a single call....

That's because each opcua- component is a separate crate, therefore each has to say its dependencies in the Cargo.toml. It might be possible in 0.10 to refactor the codebase from...

I'll leave this open to take a look at it. Up until now all the enums have been the same length so it hasn't required any special code.

Some clients such as dataFEED OPC UA client still seem able to extract the Argument info. I can only assume they're looking at the variable's DataType to assume the value...

It's likely to be a bug somewhere rather than intended behaviour. You can see that the numbers are sequential but one went missing somewhere...

Issue #17 is similar to this too. I'm playing around with the client api at the moment to make it a little simpler to manage. The standard way to connect...

I've updated the code on the trunk to do the following. If your client connects to opc.tcp://foo/xyz but the server advertises opc.tcp://bar/xyz then the client substitutes *its* hostname in the...

Hi, sorry for not looking at this sooner, but it looks like you're trying to infer the hostname from the application uri but the OPC UA spec describes the application...

At present they're synchronous only. You could poll the current value and have your own thread in the background which refreshes that value.