Hi All, I've been thinking further about this problem, and decided to look at changing the .Net plugin to strip off content length, as this avoids the multiple buffered reads for content of unknown length, which is where I encountered problems previously. With the content length info I can now read the whole embedded content into a single data structure that I've added to the osgDB module, that has similar functionality to the istream/socketbuffer. I've got some tidying up to do, however the principles proven. Once I'm happy with it I intend to release it as a submission/contribution for Robert to consider adding to the code base in the future.
On that note, what is the protocol for making a submission? What standards should the code conform to - even though developing on Windows platform, I'm coding standard c/c++ only. Anyway, thanks for the help, and the sounding board for ideas. Cheers Neil. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
