As far as I understand, the page rendering is always done on-the-fly, that is, there is a component pool and when some page needs one, the pool quickly provides it. Now, thinking what Chris originally asked, is there too much overhead if I have a page with, say, 20 components? Or 50? If a page has deeply nested components and many many variables to bind (doing it both in the rewinding and the processing phases), Tapestry of course would be a much better option over JSPs or similar, but is there an inflexion point where one would be indeed abusing the concept?
PS. Proof-reading my own post I realize this is kind of a silly question, since such a complex page should never exist and would be a problem not only for any framework but also for any user... :-) On 8/5/05, Kevin Menard <[EMAIL PROTECTED]> wrote: > On Friday 05 August 2005 19:13, Robert Zeigler wrote: > > > My point was simply that, just because you can't reuse the component > > across multiple projects doesn't mean it shouldn't be a component. :) > > (Or, there's nothing wrong with application-specific components. :) > > Ahh good, then we're in agreement :-) > > -- > Kevin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Hay dos tipos de mujeres: las bonitas y las que se pintan. - Enrique Jardiel Poncela --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
