Is MapServer Thread-safe?

[Adrian Kruk]

>The most fundamental components can be used safely right now that are
>protected with locks. 

Safely yes, but with lower performance. 
Function msAcquireLock is called 50 times. Maybe it is possible to try to
less this number one by one, or better starting from ones which are called
the most often.

Can help, but as understand RFC15 has not started yet.

>- Reviewing all the portions of the mapserver and the dependent libraries code

Is it means that mapserver could has code which you aren't sure that is
stable in multithreading calls (or you are sure that is unstable and not
locked)?

>- Create test applications that can cover most parts of the
>mapserver/mapscript code.
I can create some simpl test application to test mapscript multithreading in
VS2005 or Mono.



Regards,
Adrian