Autodesk 15606-011408-9300 Developer Guide - Page 88

Introducing ColdFusion and ASP

Page 88 highlights

Introducing ColdFusion and ASP The examples in this chapter were created using two report engines, Macromedia ColdFusion and Microsoft Active Server Pages (ASP). ColdFusion and ASP are application servers. An application server is an application that works with the Web server to provide additional Web functionality. Like the Web server, it runs in the background as a Windows® NT service. Both products work essentially the same way. You build Web pages that include special tags, and when a Web browser requests one of those pages, the application server interprets the tags, replaces them with the results of the specified calculations or database queries, and then sends the completed page to the Web server. The Web server then sends the page to the browser to be displayed. Because the processing is done by the server, the end-user sees only the final HTML output, not the code used to create that output. (Of course, the HTML can include anything- even client-side scripting code!) Although end-users can view the source of your HTML output, they never see the server-side scripting code used to create that output. This developer's guide uses ColdFusion and ASP for its examples because developing with these products is easier than writing your own Perl scripts or Visual Basic/C++ DLLs, and because these products are by far the most common platforms for Autodesk MapGuide server-side application development. ColdFusion is available from Macromedia, and ASP is included as part of Windows 2000 and Windows NT Server 4.0 with the Windows NT 4.0 Option Pack. Although the examples are specific to ColdFusion and ASP, the concepts are general, applying to Common Gateway Interface (CGI) and to other application servers as well. ColdFusion supports both Microsoft® Internet Information Server® (IIS) and the Netscape® Web servers. ASP supports IIS only, meaning that it, and your map applications, can only be run on the Microsoft Web server. Keep in mind, though, that this does not affect your users; the HTML pages you produce can be read by any Web browser. The limitation exists only for the Web server. 88 | Chapter 6 Using Reports to Query and Update Data Sources

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 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
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

88
|
Chapter 6
Using Reports to Query and Update Data Sources
Introducing ColdFusion and ASP
The examples in this chapter were created using two report engines,
Macromedia ColdFusion and Microsoft Active Server Pages (ASP). ColdFu-
sion and ASP are
application servers
. An application server is an application
that works with the Web server to provide additional Web functionality. Like
the Web server, it runs in the background as a Windows
®
NT service.
Both products work essentially the same way. You build Web pages that
include special tags, and when a Web browser requests one of those pages,
the application server interprets the tags, replaces them with the results of
the specified calculations or database queries, and then sends the completed
page to the Web server. The Web server then sends the page to the browser
to be displayed. Because the processing is done by the server, the end-user
sees only the final HTML output, not the code used to create that output. (Of
course, the HTML can include anything
even client-side scripting code!)
Although end-users can view the source of your HTML output, they never see
the server-side scripting code used to create that output.
This developer
s guide uses ColdFusion and ASP for its examples because
developing with these products is easier than writing your own Perl scripts or
Visual Basic/C++ DLLs, and because these products are by far the most
common platforms for Autodesk MapGuide server-side application develop-
ment. ColdFusion is available from Macromedia, and ASP is included as part
of Windows 2000 and Windows NT Server 4.0 with the Windows NT 4.0
Option Pack. Although the examples are specific to ColdFusion and ASP, the
concepts are general, applying to Common Gateway Interface (CGI) and to
other application servers as well.
ColdFusion supports both Microsoft
®
Internet Information Server
®
(IIS) and
the Netscape
®
Web servers. ASP supports IIS only, meaning that it, and your
map applications, can only be run on the Microsoft Web server. Keep in
mind, though, that this does not affect your users; the HTML pages you
produce can be read by any Web
browser
. The limitation exists only for the
Web
server
.