read form
display form send htmlcomplete form display results send html get results, pass to WebStar HTML results in calculation fieldSTFM 96 Web Workshop II Home
| Society of Teachers of Family Medicine | Faughnan Home Page | Elson Home Page | STFM 96 Introductory Web WorkshopThis table illustrates the flow of data during a typical web-database transaction. The columns are the domains where activities occur. In the top half of the table, the rows are increasingly specific instances of a particular domain. (Ex: user, human, John). In the bottom half of the table, each row corresponds to a particular process or transaction. The arrows show the flow of data.
| user | client | middleware | data server | |
|---|---|---|---|---|
| human | web browser | web server | [3] CGI | database |
| John | Netscape | WebStar | Web FM | FileMaker Pro |
|
||||
| click mouse |
send URL |
process URL |
||
| read form |
display form |
send html |
||
| complete form |
||||
| click "submit" |
[1,2] post data |
pass data to specified CGI |
interpret data, send AppleEvents to FileMaker |
interpret AppleEvents |
| read results | display results |
send html |
get results, pass to WebStar |
HTML results in calculation field |
CGI: common gateway interface
URL: uniform resource locator
[1] post is the most common method of sending data, often text is "url-encoded".
Get is used for searches or queries and also uses "url-encoding". Less used are:
head, put, delete, link, and unlink.
[2] Data sent includes: your machine address and possibly your name, name of server and
CGI to be used, size and type of data, and the binary data.
[3] WebFM is a compiled special-purpose CGI. ClarisFM is an AppleScript CGI. UNIX systems
often use CGI's written in Perl.Java is also a CGI programming language, though it is
unusually powerful.
STFM 96 Web Workshop II Home | Society of Teachers of Family Medicine | Faughnan Home Page | Elson Home Page | STFM 96 Introductory Web Workshop