This will sound very familiar to those who have experience of developing desktop
applications with some Rapid Application Development environments, such as
Borland Delphi or Microsoft Visual Basic. However, web applications are very
different from desktop applications, and although working with Tapestry we do
not need to deal with complexities that arise from this difference, it is useful to
understand how things work, at least in general terms.
Let's say that a Tapestry application is deployed on a web server in the USA, while
the user who came to try the application is in Australia. What the user actually
sees in his or her web browser is a piece of HTML, perhaps enhanced with images,
JavaScript, and styles, but basically this is just a snapshot. It is just one moment in the
life of the real Tapestry page, an entity that lives on the server.
When the web server receives a request from a user, it uses an appropriate Tapestry
page to generate some output??”some HTML page??”to be sent to the user. When the
user does something with the received HTML page, like putting some data into text
boxes or clicking on a button, the information on what was done there is sent back
to the Tapestry application.
Pages:
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72