Gambas Server Pages
, you have some sort of
scripter hack that allows you to write ASP-like files that I named "
Put that in a text file, make it executable, and run it.
DIM sEnv AS String
<!-- Variable declaration must come before any HTML -->
<h2>CGI script environmental variables</h2>
<table border="1" cellspacing="0" cellpadding="2">
<% FOR EACH sEnv IN Application.Env %>
<td><%= sEnv %></td>
<td><%= Application.Env[sEnv] %> </td>
<% NEXT %>
As you can see, the server page is a script, but the script executable
is 'gbw3', not 'gbs3'.
'gbw3' is actually a symbolic link to 'gbs3'. When 'gbs3' detects than it is
run from the 'gbw3' symbolic link, it knows that it will have to process a
server page and not a script. Then 'gbs3' will transform the server page
into...a normal script, and will execute it.
Except the initial line with the '#!/usr/bin/env gbw3
' magic, the syntax is
very similar to ASP pages.
- <% XXX %> introduces any Gambas code.
- <%= XXX %> evaluates a Gambas expression, translates it into HTML, and inserts the HTML inline.
Note that the gb.web component
is used by default. So you can use the Session
, the Response
object, the Request
object, and so on.
These Gambas server pages are CGI
scripts, and must be managed as any other
script in your preferred web server.