On 12/8/06, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote:
No problem with concurrency, as I said they have no state. A lot of patterns would make sense, but JSF API/taglib doesn't seem to facilitate any of them, hence my question.
Object creation and GC overhead was a very significant issue in early JVMs (10, 1.1), and has gotten to be progressively less or an issue in later versions as algorithms have improved. This has gotten to the point that with 1.3/1.4 JVMs, we started to see benchmarks where the overhead of maintaining a pool exceeded the overhead of allocating and GCing new objects every time, for a significant number of use cases (but especially in simple lightweight classes). Thus, you see the more modern APIs not implementing pooling and factories -- for example, in JSP the historical tag classes were pooled, but SimpleTag instances are not. JSF's architecture follows this modern trend. Best,
Bolerio
Craig
