Angus Dorbie (dorbie++at++sgi.com)
Thu, 15 Jul 1999 14:55:22 -0700
Performer objects must be created in the app or related processes i.e.
the database process.
Another unrelated application could pass data via shared memory or some
other form of IPC to database or app process and you could create
pfObjects based on that data.
Cheers,Angus.
ross::barna wrote:
>
> 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
>
> -----------------------------------------------------------------------
> List Archives, FAQ, FTP: http://www.sgi.com/software/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
--
Never express yourself more clearly than you think.
Neils Bohr
For advanced 3D graphics Performer + OpenGL based examples and tutors:
http://www.dorbie.com/
This archive was generated by hypermail 2.0b2 on Thu Jul 15 1999 - 14:55:28 PDT