Hi, On Thu, 2009-03-12 at 12:08 -0500, Allen Bierbaum wrote:
> A bit of both. It sounds like from a user perspective MTRecPtrs are > the way to go because you can use them and forget about memory issues. > Internally to OpenSG things get more complex because of performance > optimizations with RecPtr being the higher performance reference > counted ptr, UnrecPtr being a very strange one that still reference > counts, TransitPtr being there to prevent bugs in code, and Cptr for > the really high performance stuff. there is one piece missing, the rec and unrec tags are related to the cluster. In order to guarantee that application pointers are reflected correctly the reference counts have to be transferred to the servers, hence the recording tag. Those should be used by applications to store pointers to OpenSG objects. The unrec variant does not transmit reference counts during the cluster sync and is there to be used for temporary pointers, e.g. while creating the graph it is more efficient to use unrec pointer and only use rec pointer where the app stores a direct reference, e.g. for the root node. So the most efficient pointer is actually the UnrecPtr variant. kind regards, gerrit ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
