Leo Sutic wrote: > <snip/> > > We've agreed that all components returned from a CM are thread safe. > > <snip/> Sorry for jumping in this late but I was away during the last 5 days and tried to follow the thread of over 60 emails...but didn't directly succeeded in finding why all components must be thread safe.
If I'm looking at the current implementation of many components available in excalibur and in projects using avalon, there are many components NOT thread safe and never will be. A simple one is a parser object. Now, basically if I get a different parser object on each lookup there are no real problems - also it's still not really thread safe. But if I always get the same parser object, than this cannot work. So in order to make it work I would return a "factory" like object from which I can get a parser via getParser() or something which is than not thread safe. Would work, but if that's the case, I have to implement a "factory", the parser itself (including the "factory" interface, the parser interface) etc. and I don't see the great advantage in using a component framework anymore as I code most part myself. Am I wrong? If someone could point me to the mail, explaining how all components returned from a CM can be thread safe, I would be very happy! Thanks Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
