|
> From: Mark Phippard > > If your code is stable, then a one-time step to JAR it up is hardly a > heartache. How often is code ENTIRELY stable, Mark? Be realistic. If you're in any sort of living, breathing shop, functionality is added or changed every day. The only place code is stable is in a CS101 class. Or maybe an old S/36 shop <grin>. > Personally, I do not believe that JAR files speed the JIT or > class loading process all that much Well, you disagree with every text on JIT compilers that I've read, including the white papers from IBM. Who should I believe? The guys that write the compilers or you? > especially for web applications where you have a > lot of small loosley related classes. > It certainly helps for things like > JT400 or Struts where a large chunk of related code can all get loaded at > once. But I think for some general servlet code the difference is likely > negligible. The problem with WebFacing is the sheer volume of > classes and JSP's that have to be loaded. Why does a web application need a lot of small loosely related classes? My architecture doesn't. My architecture never adds new classes, with the exception of the JSPs. This seems a much more rational approach to web design. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.