Hi Serge, I would be good to collaborate on a single libcurl based plugin that can meet the variety of different types of usage models users will through at it. I have thrown together a very simple one right now. So far it can load databases, including hierarchical ones. I haven't implemented cache support, but I'm tempted to push cache support into osgDB and make it available to a range of plugins.
W.r.t going a mulit-threaded route where a request is made and then the data is loaded later. How do you go about implementing this? Using ProxyNode? Using your own database pager? My thought has been to change osgDB::DatabasePager so that is has one or more database threads, so push the multi-threading here, rather than into any specific plugin. Robert. On Fri, Mar 21, 2008 at 9:11 AM, Serge Lages <[EMAIL PROTECTED]> wrote: > Hi Robert, > > For our needs we already developped a libcurl based plugin, and we must say > that it works great. Currently we don't share it because it's really > dedicated to our needs (we have specific scripts directly called into the > server side to group requests for example). > > The major feature of our version is that the plugin doesn't block the calls > (except if it is asked with an option). The plugin is multi-threaded to > handle lots of requests and returns the asked object only after several > calls, before that it returns an error. As PagedLOD or ProxyNode requests > nodes as long as it doesn't have any return it works great. > > We are disposed to drop our dedicated version if the new one is flexible > enough, and off course we are disposed to help on the new plugin > development. > > > > On Thu, Mar 20, 2008 at 8:41 PM, Robert Osfield <[EMAIL PROTECTED]> > wrote: > > > > > > > > > Hi All, > > > > I have done a bit of work using libcurl, and have already got a very > > basic ReaderWriterCURL written, and it looks like it'll be easy to add > > this directly into the core OSG as a new OSGPL'd plugin. > > > > Right now osgDB::Registry is hard-wired to use the existing .net > > plugin whenever there is call involving http:// in its filename. With > > a new libcurl we'd either need to change osgDB so that is detects the > > presence of the libcurl based plugin and chooses this as the plugin to > > use or replace the existing .net plugin. Retaining both would would > > complicate osgDB::Registry a little but not hugely. > > > > The other route would of replacing the existing and move the .net > > plugin out into the deprecated annex of the OSG. The upside of this > > is that it would resolve the issue of the .net plugin containing GPL'd > > code, something that doesn't sit well with the OSG's more liberal > > license, and certainly not with usage with non GPL'd applications > > (although technically runtime loading of GPL'd plugins within a non > > GPL'd harness doesn't break the GPL, in spirit of how many contribute > > to GPL'd projects its a no no.) > > > > The downside of replacing the .net plugin with a libcurl based on is > > that it adds libcurl as an external dependency. CMake handles part of > > this thanks to its ability to automatically detect libraries and > > compile the relevant parts into build system. The extra dependencies > > is easy for unices, especially linux, but for windows it'll probably > > require libcurl to be added to the 3rd party dependency package, for > > this I have to rely on the generosity of Mike Weiblen and fellow > > Windows helpers. > > > > The upside with libcurl is that is supports multiple protocols, > > including ftp, ftps, https, password handling etc. My thought was to > > forward declare CURL in osgDB and allow it to be passed in via > > osgDB::ReaderWriter::Options so that users can do custom libcurl ops > > and then let the OSG plugin do the reading. > > > > Thoughts? > > Robert. > > > > _______________________________________________ > > osg-users mailing list > > osg-users@lists.openscenegraph.org > > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > > > > > -- > Serge Lages > http://www.tharsis-software.com > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
