. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks differ from classic web frameworks in that they build a model of requested pages on the server side and the HTML sent back to the client is generated according to this model. You can think of of the model as if it was an “inverse” JavaScript DOM, meaning that: 1. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks differ from classic web frameworks in that they build a model of requested pages on the server side and the HTML sent back to the client is generated according to this model. You can think of of the model as if it was an “inverse” JavaScript DOM, meaning that: 1. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 27.2. Create server specific http/2 push support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frameworks differ from classic web frameworks in that they build a model of requested pages on the server side and the HTML sent back to the client is generated according to this model. You can think of of the model as if it was an “inverse” JavaScript DOM, meaning that: 1. it is built on the server-side 2. it is built before HTML is sent to the client 3. HTML code is generated using this model and

the server side and the HTML sent back to the client is generated according to this model. You can think of the model as if it was an “inverse” JavaScript DOM, meaning that: 1. is built on server-side Java and good old HTML: almost all web frameworks force users to adopt 5 special tags or to use server side code inside HTML markup. This is clearly in contrast with the concept of separation between represents our web application built upon Wicket and it’s responsible for configuring it when the server is starting up. Most of the times our custom application class won’t inherit directly from class

on the server side and generating the HTML to send back according to this model. You can think of the model as if it was an “inverse” JavaScript DOM, meaning that: 1) is built on server-side 2) represents our web application built with Wicket and it's responsible for confguring it when the server is starting up. ● Class Application comes with a set of confguration methods that we can override code only when a specifc event occurs. Bundle resources ● To reduce the number of requests to the server, resources can be aggregated in bundles. A resource bundle can be declared during application