4. Dreamweaver instructs the defined testing server to execute the server-side code within the page
and passes along any variables that have been specified. The URL prefix designated in the Site
Definition Testing Server category is used to invoke the page.
5. When the code is executed, Dreamweaver reads the resulting HTML code.
6. Finally, Dreamweaver uses its translator capability to substitute the dynamic data placeholders
shown in the original document with the data generated. The temporary document is deleted
from the server.
If all goes well, a page with dynamic data placeholders (shown in Figure 22-1) is replaced with the Live
Data view (shown in Figure 22-2).
If Dreamweaver encounters an error, it displays a message that explains where the process failed and suggests
some possible remedies.
Setting up for Live Data
As noted in the summary of how Live Data works, several values found in the Testing Server category of the
Site Definition dialog are key to this feature??™s operation. Live Data must know the location of the site root
for the temporary page and how that location may be reached with an HTTP request. If either of these values
is not found, the attempt to switch to Live Data view is aborted and an error message appears.
Two different methods exist for accessing the testing server: locally, through a network, or remotely via FTP.
Pages:
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249