Yes, it should be. That's what the design is. If it does not work for you, it needs to be addressed like any other issue, i.e. describe the steps taken, actual behavior, expected behavior (well, we have that one), provide the code, etc.

Regards

It would work, by I'd rather suggest to increase the hold periods.

If you want to go your way, you do not have to subscribe to all of those items. One is enough. In fact, it can be ANY item on that server. Even more, it does not even have to any valid one.

Best regards

Hello.

The defaults are (in millseconds):
I cannot give you the estimate on "B", because it depends on many factors, but I expect it to be quite significant.

Best regards

Hello,

this is because most of the delay is not the actual data exchange, but a connection setup.
QuickOPC manages the connections (and disconnections) automatically, so you will see the first operation to any OPC server will take longer. Also, if you do not use the server for some, QuickOPC will disconnect and you will see the delay again.

If you are seeing it not just first time, but also later, you may need to increase the "hold period", so that QuickOPC keeps the connection open for longer time.

Any active subscriptions cause the connection be maintained open, until unsubscribed, too.

Best regards