Browse multiple nodes at a time instead of single node in one browse request.|OPC UA Standard|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Browse multiple nodes at a time instead of single node in one browse request.
Avatar
Tanuja Bhide
Member
Members
Forum Posts: 5
Member Since:
06/24/2022
sp_UserOfflineSmall Offline
1
06/02/2024 - 23:39
sp_Permalink sp_Print

Hello Team,

I'm reaching out with a question about retrieving data models through browse requests in our OPCUA client. We're currently utilizing a lazy fetching approach, which involves sending several browse requests to display the entire data model as needed. Under this setup, children are arranged under parent nodes, and users can request the details of the parent node's children if necessary. The client is capable of handling multiple requests without any performance problems, and the lazy fetching method appears to be effective for both us and our customers. However, I'm curious about your opinions regarding the standard practice and OPCUA compliance, and what recommendations would you offer in the context of lazy vs eager fetching or browse multiple nodes in single request vs browse nodes in successive requests lazily?

Information_model

Thanks

Avatar
Randy Armstrong
Admin
Forum Posts: 1568
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
06/03/2024 - 09:34
sp_Permalink sp_Print

It is not clear what you are comparing it with. It is generally recommended to only fetch nodes on demand. Clients that attempt to fetch everything in advance are likely to create performance issues for the server.

Avatar
Tanuja Bhide
Member
Members
Forum Posts: 5
Member Since:
06/24/2022
sp_UserOfflineSmall Offline
3
06/05/2024 - 18:55
sp_Permalink sp_Print

Hi Randy,
The query is in context to View Services Basic Browse - Lab Case 043

i.e to allow a server to optimize the collection of the required data, a client desired to browse 10 nodes should put all of them in one BrowseRequest instead of creating 10 BrowseRequest each only having 1 Node inside. 

Avatar
Randy Armstrong
Admin
Forum Posts: 1568
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
4
06/08/2024 - 03:50
sp_Permalink sp_Print

Yes that is the recommended approach. All servers need to support.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 11
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1435
Posts: 4861