pfDataPools and pfNodes

New Message Reply Date view Thread view Subject view Author view

ross::barna (rbarna++at++umich.edu)
Thu, 15 Jul 1999 15:34:33 -0400 (EDT)


ok, after much confusion i have realized that i CANNOT new a pfObject in a
pfDataPool.

my goal was to allow unrelated (non-forked) processes to attach their
scene graphs to a displaying performer process. to do this, i cannot use
pfSharedArenas because they are different for the unrelated processes
due to their individual calls to pfInit(). so, i needed to use
pfDataPool.

pfDataPool can allocate memory for objects quite well, and unrelated
processes attach cleanly. the problem is the little known pfUpdatable
object that looses the ability to new into an arena other than the one
made by pfInit()!!!! check the headers for pfObject (has the new(arena))
and pfNode and you will see that the pfNode looses it's new(arena)
somewhere inbetween!! namely pfUpdatable.

why is this?

what can i do to work around this feature?

remember, that i need to allocate memory between UNRELATED processes.

please help!!!!!!

-ross

_____________________________
ross::barna
joga.ummu.umich.edu


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Thu Jul 15 1999 - 12:34:22 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.