Like I said, we're pretty clearly not going to agree. I see no advantage to witholding a good example that is itself useful only because a newbie might extrapolate too far; I see lost opporunity and buggy ad hoc implementations resulting from not providing the solid example.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Igor Stasenko Sent: Thursday, October 22, 2009 11:35 PM To: [email protected] Subject: Re: [Pharo-project] Thread-safe collections 2009/10/23 Schwab,Wilhelm K <[email protected]>: > Sig, > > That's fine as far as it goes, but the building blocks are useful both as > concrete components and as examples of how to protect something. > yeah, and given these examples one could easily write a thread-unsafe application. But then, when it doesn't working as expected, he scratching his head and saying: hey, what's going on! I'm using a thread-safe library, why the heck my application not thread-safe?!?! And instead of start writing a concurrent, thread-safe code, he chooses to write another library, which will be 100% thread-safe and then he can be 'assured' that his thread-unsafe code will magically become thread-safe because he using a 'right' tool :) > Bill > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Igor > Stasenko > Sent: Thursday, October 22, 2009 11:01 PM > To: [email protected] > Subject: Re: [Pharo-project] Thread-safe collections > > 2009/10/23 Schwab,Wilhelm K <[email protected]>: >> Sig, >> >> It appears we are not going to agree. >> > It appears not. > > Thread-safe collections is too good to be true solutions for concurrency. Its > too simplistic approach and in a long run , fairly ineffective. > In any real-world application the basic building blocks is not generic > collections, but different objects which composing your domain model. > Some of your domain objects could use collections, some of them not. > But you can't predict how do they using them , and in what way to state that > putting thread-safe collection in use will make the whole model thread safe. > And that's why i think thread-safety should be introduced at higher levels of > abstractions. > >> Bill >> > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
