title: Wicket: “large memory footprint!”, "Does Wicket scale?".. etc
body: <p>Wicket uses the Session heavily which could mean “large memory footprint” (as stated by some developers) for larger apps with lots of pages. If you were to explain to a bunch of CTOs from Fortune 500 that they have to adopt <a href="http://wicket.apache.org/" rel="nofollow">Apache Wicket</a> for their large web application deployments and that their fears about Wicket problems with scaling are just bad assumptions; what would you argue?</p>
  
  <p><strong>PS:</strong></p>
  
  <ul>
  <li>The question concerns only
  scaling.</li>
  <li>Technical details and real world
  examples are very welcomed.</li>
  </ul>