On Friday 27 August 2004 05:56, Curt Zirzow wrote: > I was reading the TODO list earlier today and noticed the item > about adding ¬e.not-threadsafe; to stuff that isn't thread safe. > And a new module is added in PECL mentioning it probably isn't > thread safe. So that got me thinking... > > grepping for threadsafe seems to result in NULL. So I'm assuming > this task hasn't been started.
Yes, thats right. > So, what we might want to do is assume all modules/functions are not thread > safe. And add an entity that signifies the whole module or > paticular function *is* thread safe. > > Using this approach might seem more feasable, since basically an > audit must be done in order to flag the section as thread safe. > > This might need some cooperation with internals and a method of > flaging modules/functions as thread safe within php-src, cause > ideally I'm looking at a situation where a person can configure php > like: > > ./configure --thread-safe-only ... > So if one truely desires to use a threaded SAPI (apache2) with PHP > they can figure out what should and shouldn't be compiled until the > ideal situation is obtained. > > Any thoughts on this? Thread saftey has been discussed on internals many times. AFAIRC the conclusion was, that it isn't possible to determine thread saftey, because of many unknown issues (underlying libraries, different OS'es, and so on...) For more precise info you could search the archives of internal;-) Friedhelm -- http://www.jungle-world.com/
