https://bz.apache.org/bugzilla/show_bug.cgi?id=65124
--- Comment #19 from John Engebretson <jeng...@amazon.com> --- We had a working version that chunked the jspService method, but dropped it because our use cases didn't need it... and the whole package was already pretty complex. Unfortunately I can't find the source. What I remember: 1. Generate the overhead (aliasing, try/catch, etc.) 2. Call a chunk1() method, with content generated later 3. Store up tags, output, etc. for the not-yet-created chunk1 4. Every so often (5 tags, 30 branches, whatever) switch to chunk2, 3, etc. 5. At the end, iterate through the accumulated chunk info (step #3 above) and generate the methods. Memory usage wasn't bad in our cases, but if necessary the chunkN() methods could be written to temp files then copied in when ready. One comment: "So anything that can reduce the amount of generated code in the _jsp_service method should be a priority." There seems to be tension between improvement for all cases, vs. support for an extreme case. A stronger argument for this concern is to maintain backwards compatibility (which I agree with 100%). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
