Re: T1lib thread safety

On Fri, 12 Apr 2002 22:00:12 -0700 (PDT), Rasmus Lerdorf wrote: >Just the tip of the iceberg. There are a bunch of libraries that PHP can >talk to that are not threadsafe. It's going to take a while before >Apache2+PHP is going to be useful. Maybe we need to make a list of libraries that indicates which are thread safe & which are not. What about the other SAPIs? There are 9 that specify PHP_BUILD_THREAD_SAFE. Don't they break too? >For GD specifically, yes we can put in some mutexes as I earlier today put >a copy of the GD library into PHP CVS so we can fiddle with it and >distribute our own modified GD with PHP. I was actually thinking of just the GD PHP extension as the GD library itself doesn't call t1lib. It's the ImagePS* functions that do. >On Sat, 13 Apr 2002, Brian Havard wrote: > >> While doing some testing with Apache 2.0.35+PHP4.2.0RC3 I'm getting random >> crashes in T1_LoadFont(). Looking through the t1lib source (v1.3.1) I see >> frequent use of global variables which suggests it isn't thread safe. Is >> this a known problem? Maybe some mutexes in GD would help.... -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh@kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------