Derick Rethans a écrit : > On Tue, 27 May 2008, Gaetano Giunta wrote >> C - what about an ezcMutex component, to be used when synchronizing >> execution of stuff between >> + different php treads or processes on a single server >> + different php servers (sharing either a disk storage area or a db) >> the basis is of course the ezmutex code, taking into account the >> fact that in lots of cases flock is not available or not dependable. >> Tieins or subclasses can be used to implement the lock via: shmem >> (apc/eacc/memcache ???) / dio / flock / db code >> > hmm, I have to admit that I don't really understand what you're trying > to solve with this. Well, mutexes are used in a few places in eZPublish, and when they are not working Bad Stuff (TM) happens. Such as images getting randomly deleted. Maybe there could be workarounds to the mutex approach, but so far we have been more busy trying to pinpoint the problem and fixing it than rethinking eZ inner workings... > Mutexes are generally used to make sure that only > *one* application/process/thread can access a specific resource. Doing > this usually hurts performance of applications (because they have to > wait for the mutex to be free). This is why usually you only use mutexes > where it is *really* required and *no* other solution can possibly work. > I fully agree. And yet, if there is no true and trusted solution, coders might try to implement ad-hoc, broken ones, instead of steering clear from the stuff and rethinking the solution. And, depending on the current php setup, the correct solution might involve using one of the technologies mentioned above but not the others...
bye Gaetano > regards, > Derick > > -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
