Hey Jeremy, thanks for the info. I am having a hard time seeing how Wicket uses less memory if for each user/page it keeps a DOM tree of objects in memory + any model data for that page.. where at least in my struts2 apps, there is nothing in memory on the server side.. only when a request comes in do I load some data, then send it back as part of the response. The memory is then GC'd at some point by JVM.. but there is no object tree or anything else related to the user, page they are on, etc in memory at all. So I am not sure how Wicket can use comparable if not less memory when the struts/mvc way with a stateless request flow uses pretty much no memory.
One day, if a startup I work at takes off and I make enough mula to not have to work, I would love to write an app in spring, struts, wicket, couple others.. and compare the details and differences. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4087996.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
