From: Goncalo Carvalho (g.carvalho++at++gsa.ac.uk)
Date: 03/25/2003 06:05:56
Hey,
>
> well, I guess you're right in implementing this threading model. So I'll
> have to look forward in this way.
Not necessarily. It's just one way of doing things that matches my
requirements.
> But I read in some older articles that performer internally is based on
> sproc threading and therefore can get into seriously troubles when
> mixing with pthreads. Did they change their internal coding with respect
> to pthreads ?
I never got into trouble, but you should proceed cautiously ;). I think
there
was a replacement of sproc that allows you to do this. Anyway I never
encountered any problems using Performer 2.5 and above in all 3
platforms. But again
I use threads in controlled ways and I tend to use the Performer
processes for tasks
related to the scene graph itself.
>
> Again a question about shared memory: Infact, using 2 communicating
> processes will need to implement an interprocess communication based on
> shared memory. But aren't 2 threads (spawned from 1 process) actually
> using the same portion of memory ?
>
You can also send private data to the thread. Using the shared memory in
Performer is a way to
insure that all Performer processes can see the data. You may not need
to do that (e.g. if your multiprocess mode is PFMP_APPCULLDRAW). Depends
on the
application.
Goncalo
-- Goncalo Carvalho Digital Design Studio - Glasgow School of Art House for an Art Lover - Bellahouston Park 10 Dumbreck Road Glasgow G41 5BW United KingdomTel: +44 (0) 141 353 4616 Fax: +44 (0) 141 353 4422 Mobile: +44 (0) 7766 295867 mailto:g.carvalho++at++gsa.ac.uk
This archive was generated by hypermail 2b29 : Tue Mar 25 2003 - 06:11:11 PST