On Mon, Mar 31, 2014 at 1:27 PM, Mark Eggers <its_toas...@yahoo.com> wrote:
> As far as Glassfish versus Apache Tomcat goes, they address different use > cases. Glassfish is a J2EE application server. Apache Tomcat is a servlet > container. While you can convince Apache Tomcat to do a lot of things, at > some point it's better to run an application server if your requirements > dictate it. Apache TomEE is a good choice. > +1 TomEE is a good choice, and it makes you a Tomcat user, too. :) > > BTW, I like Glassfish and Apache TomEE. It just depends on my use case. > As one that migrated from Glassfish to TomEE, my recommendation is TomEE. > Concerning string concatenation, I think you would be surprised. Since > strings are immutable, concatenating strings is very expensive if you're > doing more than a few. I believe I read somewhere that concatenating 'n' > strings is proportional to the quadratic of n. In short, ouch. Are there > better places to spend time on optimization? Probably, but this depends on > your application. Is concatenating 100 strings using the concatenation > operator needlessly expensive? Most probably. > In the past, i worked on a contract where I moved some string-processing Powerbuilder logic from PowerBuilder/client to database stored proc. Previously, the Powerbuilder client-side string-processing code took 1.5 hours to complete; after i moved the logic to database stored proc, it took 2 to 10 seconds to complete. :)
