On Sun, Mar 25, 2007 at 11:02:50AM +0200, fdegrassi wrote: > I already did it using a service, what i do not like of it is that > services are (obviously) stateless, not pooled, so i can't use them in
While they are not pooled, they are not necessarily stateless. Services have access to the session and to ASOs just as everything else. It certainly makes sense for tapestry to pool pages, but it would not make sense to pool services in that sense, because there is nothing tapestry has to do, like parsing the template, wiring the components. Hence, I do not see the advantage of (ab)using a page to render a png. What should tapestry pool here, and how should it know how to do it? Other markups (like SVG) would be another case. There is a lot of reuse potential. Regards, Christian -- Christian Haselbach - [EMAIL PROTECTED] - +49 176 2082 5804 TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring Geschäftsführer: Henrik Klagges, Gerhard Müller, Eike Reinel Amtsgericht München, HRB 135082 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
