On Wednesday 13 Jan 2010 16:45:01 Robert Osfield wrote: > 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.
That's what I suspected. Do I understand you correctly, though, that for ProxyNode once a child has been loaded it is considered final and no further attempts at loading will be done? > > 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. That gives me an avenue to pursue. I originally thought of adding a blacklist directly into the curl plugin, as that plugin has direct access to the return code of the web-server. But Registry::ReadFileCallback seems more flexible and could of course be used irrespective of which loader plugin is used. > > 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. If ProxyNode/PagedLOD were enhanced with a black-listing feature, what would be your preferred way to switch it on or off? > > Robert. Many thanks, Magnus _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
