> -----Ursprüngliche Nachricht----- > Von: Jim Jagielski > Gesendet: Donnerstag, 14. Mai 2009 14:46 > An: dev@httpd.apache.org > Betreff: Re: slotmem API notes
> > In general, I think that a provider should know if it is thread-safe > or not and simply "work" without the user needing to know or worry. > I think if the provider knows that threads are available AND the MPM > is threaded, it should by default mutex as required instead of having > users all need to recreate that externally. If the user says "I don't > care what MPM I have, don't worry about locking", then I am +1 on a > flag of some time telling the provider to bypass that. > > Even so, then, I think that we should expose lock/unlock if we make > this a user-land "you decide if you want to do it or not"... I don't > think it makes sense having the user/caller have to worry about > re-inventing the wheel as far as mutexes are concerned just to > use a provider... A provider should provide the full set of functions > the end-user should need in order to use it. (imo) +1 Regards Rüdiger
