Joakim, you took the words right out of my mouth. It seems, in distributed computing with a solid versioning mechanism, that everything that can be moved to a build-time operation is a (potentially) huge win for global cost/performance.
j On Jun 18, 2:40 pm, Joakim <joakim.edenh...@gmail.com> wrote: > I've been pondering for some time now why none of the frameworks seem to > have realized that the configuration will never change after the build is > complete. They should all ship something that generates an XML config from > the class annotations (Ant plugin, an annotation processor for javac, > anything), I can't imagine the amount of resources wasted globally because > of the lack of this (though that likely says more about my imagination than > anything else). > > My project: > > # of classes in WEB-INF/classes: > Zero (I jar) > > Size of WEB-INF/classes: > 0M > > # of jars in WEB-INF/lib: > 44 > > Size of WEB-INF/lib: > 34.5M > > # of classes registered with Objectify: > Zero (I still haven't moved from JDO) > > # of classes registered with other means (any explicit classloading, ie > JAX-RS): > 100+ > > Fastest observed startup time: 35s > Typical startup time: 45s > Slowest startup time: deadlined 60s+ > > > > > > > > On Monday, June 18, 2012 9:58:29 AM UTC+2, Jeff Schnitzer wrote: > > * My "sitemap" (ie the mapping of URIs to code) is determined by > > @Path annotations on 80+ classes. This is the JAX-RS way. The > > alternative is the history of defining all URIs in xml files like > > web.xml or struts.xml - an approach that was wholly abandoned by the > > Java community at least 5 years ago. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
