ChristopherSchultz commented on pull request #351: URL: https://github.com/apache/tomcat/pull/351#issuecomment-697473351
@rotty3000 This is what I was thinking would be better than post-processing. The JSP->class translation should be a one-time hit rather than a filtering-step that requires CPU time and possibly more buffering for each response. @markt-asf Reducing useless whitespace and compression are both ways of reducing the overall bulk of a response. In one case (whitespace) you are removing literally useless data. In the other case, you are retaining *all* the useful data but reducing the size. The two together are better than either one alone IMO. But comparing the two directly is a false equivalence: it's not fair to say "you get a bigger benefit from using gzip vs. whitespace trimming" because they are different things. Not trying to cause a big fight; just mentioning that they are both pieces of a larger puzzle. Finally, a post-processing HTML-reducing filter would be useful for situations where JSP isn't being used _at all_ and might be a superior solution merely due to its flexibility. There are those performance considerations, though, of course. But we are talking about a trade-off between (essentially) CPU usage and network bulk, so there will always be a trade-off. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
