>-----Original Message----- >From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] >Sent: 20 February 2004 14:26 >To: JMeter Developers List >Subject: Re: Possible Thread enhancements > > >If this how it's working?
Well, I think so - I was thinking of having a debug flag which caused the get/set methods to make appropriate checks: - has the field been initialised already - is the threadName the same. > >Yes, it would make sense to keep the context somewhere that can be >accessed easily. The solution you propose sounds good. Maybe we should >make that part of the TestElement interface (and of course >implement it >in the AbstractTestElement). > >BTW, what's the mechanism used by the engine to decide which elements >need to be cloned per thread and which don't (I'm assuming listeners >don't, since they gather data from all threads). Don't know for sure - I think there is an Interface that is used to tell it not to clone certain classes. In theory one could find this out from the Javadoc ;-) S> ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
