HI Magnus, The ProxyNode doesn't know anything about database loading, all it knows that it can make requests for children to be loaded and it'll keep doing it per frame in non have been loaded yet.
Whether you want to black list a child that fails to load is something that the OSG can't decide by itself, and the missing files can appear later in the life of the application. User applications can decide though, using a custom Registry::ReadFileCallback you can create your own black list and issue a failure to load on each load. One possible refinement of ProxyNode/PagedLOD might be for them to allow you to black list their external file references and for this black list to be used internally to prevent further attempts at loading. I'm open to such a submission. The issue of whether to black list or not is still something that is application specific though and will need to be decided upon my the application. Robert. On Wed, Jan 13, 2010 at 10:24 AM, Magnus Kessler <[email protected]> wrote: > Loading remote osg files from a web server generally works very well when the > curl plugin has been compiled into OpenSceneGraph. However, if an osg file > contains a ProxyNode that points to a missing remote file (404) this leads to > a > storm of requests (once per frame!) for the non-existing resource. This only > seems to happen with ProxyNodes. Trying to access a missing top-level osg file > fails as expected after the 404 response. > > Is there any setting in either the curl plugin or in ProxyNode that would stop > this behaviour? > > Regards, > > Magnus Kessler > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
