Topic RSS19:06, EEST
February 21, 2014
OfflineHi,
I developed a server which exposes a huge number of nodes over multiple nameSpaces. I use a set of custom nodemanagers and the performance is excellent. Almost.
While the nodemanagers work very efficient, it is very slow to initially setup the references to ns=0, for instance the “typeDefinitionOf” references. With > 700k nodes and even more references, this virtually takes “forever”.
Is there any way to intercept the browse service calls of the rootNodeManager in order to “add” the references on demand – similar to what can be done with the custom nodemanager?
Thanks, Hans-Uwe
7:03, EEST
December 21, 2011
OfflineYes, you can use the NodeManagerListener or override NodeManagerUaNode the same way.
There’s also been a task to optimise the initialisation of the reference initialisation in respect to SDK 2.0. If you contact the support, we will provide you a beta version, if we get such improvements available – we will check this right now.
13:15, EEST
December 21, 2011
OfflineTaking another look, it seems that it’s not currently possible to add references on the fly, as you would need in the NodeManagerListener, which you would need to be able to modify NodeManagerRoot. But we will consider a new method in the listener, getReferences(), which would enable you to add custom references when requested.
What I talked about optimising the reference initialisation obviously will not help you.
8:10, EEST
December 21, 2011
Offline20:38, EEST
February 21, 2014
OfflineJouni Aro said
NodeManagerListener.onGetReferences() is now added to the latest internal beta version. Just send an email to get it for a test…
The #onGetReferences() callback did unfortunately not make it into the recent 1.5.0 release. Would it be possible to get a patch which adds this back again?
Thanks, Hans-Uwe

Log In
Register