[PHP_MAPSCRIPT] Tracking bug for PHP MapScript thread safety

[dmorissette]

There are still a few things to fix in PHP MapScript in order to be able to use 
it with PHP loaded as an Apache DSO.  

This is definitely is a hot topic and there are many bugs indirectly related to 
this.  This bug is to track progress towards making PHP_MAPSCRIPT work again 
with the PHP DSO. 

All indirectly related bugs should be marked as depending on the current bug.

[dmorissette]

The following bug appear to be related to this issue:

bug 77 - intermittent crash with ms_LoadMap()
bug 66 - PHP MapScript - Runaway process problems
bug 339 - Thread-safety issue un setSymbolSet()
bug 152 - Get rid of chdir() for relative paths 

[dmorissette]

I have started work on that and committed a new version to the 4.1 CVS at the
end of September that should work with PHP as a module and includes (hopefully)
the proper initializations,etc.

however this is still not fully tested.  Any brave soul who would like to help
by testing PHP MapScript with the PHP module is welcome to try the 4.1 CVS and
report issues via bugzilla.

[dmorissette]

The following question/answer seen on the PECL-dev list could be useful at some
point... adding it here just in case.

> Hi,
> are there any Zend API functions which I could use to ensure thread safety
of
> extension using thread-unsafe library? (some mutex calls or sth similar)
>
> -- 


> Yep, take a look in ext/yaz at how it uses tsrm_mutex_lock() and
> tsrm_mutex_unlock().
> 

[dmorissette]

Those bugs should be tested again with version 4.4

[dmorissette]

Marking as fixed. 

Bug 1322 (a.k.a bug 67, filename collisions in saveWebImage()) was the last
issue that kept being reported and has just been fixed.