> I'd expect it to be optional, of course.
>
> For instance, after it's been transmitted to all cluster servers or
> contexts, one could call "releaseClientStorage()" on these objects
> and the only place the data would exist is on the GL side.
>
> (And, since you can read-back data, you could implement that as well,
> if you really needed to retrieve it and send/store it somewhere.)

This might get very nasty when you want to save the scene as a OSB file 
to disk. Maybe the thread trying to write to disk is not the one that 
renders the scene ?

Matthias
-- 
+---------------------+----------------------------+
| VREC GmbH           |                            |
| Matthias Stiller    |                            |
| Robert-Bosch-Str. 7 | tel:    +49 6151 4921034   |
| 64293 Darmstadt     | web:    http://www.vrec.de |
| Germany             | mail:   [EMAIL PROTECTED]         |
+---------------------+----------------------------+

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to