ok so as long as i have no instance variables ( or read only data initialized at startup) the component will be stateless. So there is no attribiutes ihave to set in componets.xml which say this component is stateless.
i asked this question about stateless bec our application would have very very heavy load and i was thinkin that like servlets it will be better if few components can handle all the requestes instead of creating new instances. thanks wasiq > -----Original Message----- > From: Robert McIntosh [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 30, 2003 3:15 PM > To: Avalon framework users > Subject: Re: what container will be appropriate for use with web based > application? > > > One that maintains no client/caller state between method invocations, > just like EJB Session beans (stateless ones obviously), and they > certainly have a lifecycle to them. In avalon a component could be > Configurable, Initializable, etc., all of which are lifecycles. > > Making a component stateless doesn't by default make it thread safe > though. Just like with servlets, you should make sure that > any resources > a components holds on to are either synchronized or are thread safe > themselves. > > Robert > > Ulrich Mayring wrote: > > >Stephen McConnell wrote: > > > > > >>Both Fortress and Merlin support stateless components. > >> > >> > > > >Which makes me wonder: what is a stateless component? One that is > >thread-safe? One that has no lifecycle? > > > >Ulrich > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
