I miss the ability to wire a cluster reference to (un)bundle by name nodes. If I have some parallel processes that share a common configuration bundle for my project, I'd really like to be able to only have one copy of the bundle in memory. This is possible if I use a reference to a cluster. However if I do that it gets really complicated to get access to the content of the bundle. If I use 'property node --> value --> unbundle' I load the bundle into memory anyway in an extremely inefficient way before extracting the control of interest. If I use 'property node --> controls --> index --> variant to data, everything is suddenly very fragile to cluster changes, not to say needlessly complicated.
If you could (un)bundle a control directly from the cluster reference you would have easy and very efficient access.
What should then happen for non control references? I'd say the same as 'property node --> value' with the name of the control displayed. It could even be possible to access variant data by using the variant --> cluster -->variant functions.
Of course this method is subject to race conditions, but that is always the case when you use references anyway.
I'm currently working on a project where I have 9-11 active parallel processes where each process needs access to the configuration cluster. Thus I have 9-11 copies of all my configuration data in memory all the time. I'd really love to reduce that number to one.
This is my first post here. I did check for similar ideas, but I didn't find one.
-Henrik, Denmark
Any idea that has not received any kudos within a year after posting will be automatically declined.