Yes, although the actual content of the control is quite lengthy and generated recursively, and using the IMarkupWriter is a nice convenience. If I go that route it would be nice to cache the writer or at least its internal buffer.
But I wanted to make sure there is not a better way to do this since it seems like a somewhat common performance optimization and Tapestry contains direct support for other types of optimizations. On 4/24/05, Patrick Casey <[EMAIL PROTECTED]> wrote: > > Couldn't you just override the control's render method? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
