[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gawk-diffs] [SCM] gawk branch, gawk-4.1-stable, updated. gawk-4.1.0-867
|
From: |
Arnold Robbins |
|
Subject: |
[gawk-diffs] [SCM] gawk branch, gawk-4.1-stable, updated. gawk-4.1.0-867-g693ca0a |
|
Date: |
Wed, 13 Apr 2016 18:18:48 +0000 |
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gawk".
The branch, gawk-4.1-stable has been updated
via 693ca0a2c40ebfdc73f29a5696a4b0d3de0c71dc (commit)
from 20228fe368c59227b601f1ccccaeb7b6370b7848 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://git.sv.gnu.org/cgit/gawk.git/commit/?id=693ca0a2c40ebfdc73f29a5696a4b0d3de0c71dc
commit 693ca0a2c40ebfdc73f29a5696a4b0d3de0c71dc
Author: Arnold D. Robbins <address@hidden>
Date: Wed Apr 13 21:18:31 2016 +0300
General cleanups in doc/gawkinet.texi.
diff --git a/doc/ChangeLog b/doc/ChangeLog
index d21d9af..903c78f 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,9 @@
+2016-04-13 Arnold D. Robbins <address@hidden>
+
+ * gawkinet.texi: Some general cleanups. Remove stuff commented
+ out since 2001, index RFCs, change function name convention to
+ match main gawktexi.in. Update the update month.
+
2016-04-04 Arnold D. Robbins <address@hidden>
* gawktexi.in, gawkinet.texi: Enable use of braces in
diff --git a/doc/gawkinet.info b/doc/gawkinet.info
index 5b989fb..d5a7abf 100644
--- a/doc/gawkinet.info
+++ b/doc/gawkinet.info
@@ -871,7 +871,7 @@ also closes the connection. Try replacing '"NAME"' with
your login name
(or the name of someone else logged in). For a list of all users
currently logged in, replace NAME with an empty string ('""').
- The final 'close' command could be safely deleted from the above
+ The final 'close()' command could be safely deleted from the above
script, because the operating system closes any open connection by
default when a script reaches the end of execution. In order to avoid
portability problems, it is best to always close connections explicitly.
@@ -1227,11 +1227,11 @@ the HTML content of the web pages to refer to the home
system.
Each server that is built around this core has to initialize some
application-dependent variables (such as the default home page) in a
-procedure 'SetUpServer', which is called immediately before entering the
-infinite loop of the server. For now, we will write an instance that
-initiates a trivial interaction. With this home page, the client user
-can click on two possible choices, and receive the current date either
-in human-readable format or in seconds since 1970:
+procedure 'SetUpServer()', which is called immediately before entering
+the infinite loop of the server. For now, we will write an instance
+that initiates a trivial interaction. With this home page, the client
+user can click on two possible choices, and receive the current date
+either in human-readable format or in seconds since 1970:
function SetUpServer() {
TopHeader = "<HTML><HEAD>"
@@ -1267,12 +1267,12 @@ same time of day although time advances each second.
document stored in the parameter 'Prompt', it closes the connection and
waits for the next request. When the request comes, a log line is
printed that allows us to see which request the server receives. The
-final step in the loop is to call the function 'CGI_setup', which reads
-all the lines of the request (coming from the browser), processes them,
-and stores the transmitted parameters in the array 'PARAM'. The
+final step in the loop is to call the function 'CGI_setup()', which
+reads all the lines of the request (coming from the browser), processes
+them, and stores the transmitted parameters in the array 'PARAM'. The
complete text of these application-independent functions can be found in
*note A Simple CGI Library: CGI Lib. For now, we use a simplified
-version of 'CGI_setup':
+version of 'CGI_setup()':
function CGI_setup( method, uri, version, i) {
delete GETARG; delete MENU; delete PARAM
@@ -1314,7 +1314,7 @@ as well as the body.
On each subsequent run through the main loop, one request from a
browser is received, evaluated, and answered according to the user's
choice. This can be done by letting the value of the HTTP method guide
-the main loop into execution of the procedure 'HandleGET', which
+the main loop into execution of the procedure 'HandleGET()', which
evaluates the user's choice. In this case, we have only one
hierarchical level of menus, but in the general case, menus are nested.
The menu choices at each level are separated by '/', just as in file
@@ -1341,7 +1341,7 @@ browsers support the not very well-known '.xbm' format,
which may
contain only monochrome pictures but is an ASCII format. Binary images
are possible but not so easy to handle. Another way of including images
is to generate them with a tool such as GNUPlot, by calling the tool
-with the 'system' function or through a pipe.
+with the 'system()' function or through a pipe.
---------- Footnotes ----------
@@ -1359,7 +1359,7 @@ File: gawkinet.info, Node: CGI Lib, Prev: Interacting
Service, Up: Interactin
<http://www.netfunny.com/rhf/jokes/99/Mar/http.html>
In *note A Web Service with Interaction: Interacting Service, we saw
-the function 'CGI_setup' as part of the web server "core logic"
+the function 'CGI_setup()' as part of the web server "core logic"
framework. The code presented there handles almost everything necessary
for CGI requests. One thing it doesn't do is handle encoded characters
in the requests. For example, an '&' is encoded as a percent sign
@@ -1459,11 +1459,11 @@ is the code:
MENU[i] = _CGI_decode(MENU[i])
}
- This isolates details in a single function, 'CGI_setup'. Decoding of
-encoded characters is pushed off to a helper function, '_CGI_decode'.
-The use of the leading underscore ('_') in the function name is intended
-to indicate that it is an "internal" function, although there is nothing
-to enforce this:
+ This isolates details in a single function, 'CGI_setup()'. Decoding
+of encoded characters is pushed off to a helper function,
+'_CGI_decode()'. The use of the leading underscore ('_') in the
+function name is intended to indicate that it is an "internal" function,
+although there is nothing to enforce this:
function _CGI_decode(str, hexdigs, i, pre, code1, code2,
val, result)
@@ -1496,9 +1496,9 @@ to enforce this:
This works by splitting the string apart around an encoded character.
The two digits are converted to lowercase characters and looked up in a
string of hex digits. Note that '0' is not in the string on purpose;
-'index' returns zero when it's not found, automatically giving the
+'index()' returns zero when it's not found, automatically giving the
correct value! Once the hexadecimal value is converted from characters
-in a string into a numerical value, 'sprintf' converts the value back
+in a string into a numerical value, 'sprintf()' converts the value back
into a real character. The following is a simple test harness for the
above functions:
@@ -1574,19 +1574,19 @@ and append the following code:
TopFooter = "</BODY></HTML>"
}
- 'SetUpServer' is similar to the previous example, except for calling
-another function, 'SetUpEliza'. This approach can be used to implement
-other kinds of servers. The only changes needed to do so are hidden in
-the functions 'SetUpServer' and 'HandleGET'. Perhaps it might be
-necessary to implement other HTTP methods. The 'igawk' program that
-comes with 'gawk' may be useful for this process.
+ 'SetUpServer()' is similar to the previous example, except for
+calling another function, 'SetUpEliza()'. This approach can be used to
+implement other kinds of servers. The only changes needed to do so are
+hidden in the functions 'SetUpServer()' and 'HandleGET()'. Perhaps it
+might be necessary to implement other HTTP methods. The 'igawk' program
+that comes with 'gawk' may be useful for this process.
When extending this example to a complete application, the first
-thing to do is to implement the function 'SetUpServer' to initialize the
-HTML pages and some variables. These initializations determine the way
-your HTML pages look (colors, titles, menu items, etc.).
+thing to do is to implement the function 'SetUpServer()' to initialize
+the HTML pages and some variables. These initializations determine the
+way your HTML pages look (colors, titles, menu items, etc.).
- The function 'HandleGET' is a nested case selection that decides
+ The function 'HandleGET()' is a nested case selection that decides
which page the user wants to see next. Each nesting level refers to a
menu level of the GUI. Each case implements a certain action of the
menu. On the deepest level of case selection, the handler essentially
@@ -1675,8 +1675,8 @@ the set of possible answers:
return answer
}
- In the long but simple function 'SetUpEliza', you can see tables for
-conjugation, keywords, and answers.(1) The associative array 'k'
+ In the long but simple function 'SetUpEliza()', you can see tables
+for conjugation, keywords, and answers.(1) The associative array 'k'
contains indices into the array of answers 'r'. To choose an answer,
ELIZA just picks an index randomly:
@@ -1909,7 +1909,7 @@ may shape the future of networking.
We often refer to the site-independent core of the server that we
built in *note A Simple Web Server: Simple Server. When building new
and nontrivial servers, we always copy this building block and append
-new instances of the two functions 'SetUpServer' and 'HandleGET'.
+new instances of the two functions 'SetUpServer()' and 'HandleGET()'.
This makes a lot of sense, since this scheme of event-driven
execution provides 'gawk' with an interface to the most widely accepted
@@ -2073,7 +2073,7 @@ variables in a file, and a concurrent process in the
embedded system may
read the file. The program uses the site-independent part of the simple
web server that we developed in *note A Web Service with Interaction:
Interacting Service. As mentioned there, all we have to do is to write
-two new procedures 'SetUpServer' and 'HandleGET':
+two new procedures 'SetUpServer()' and 'HandleGET()':
function SetUpServer() {
TopHeader = "<HTML><title>Remote Configuration</title>"
@@ -2090,14 +2090,14 @@ two new procedures 'SetUpServer' and 'HandleGET':
if (ConfigFile == "") ConfigFile = "config.asc"
}
- The function 'SetUpServer' initializes the top level HTML texts as
+ The function 'SetUpServer()' initializes the top level HTML texts as
usual. It also initializes the name of the file that contains the
configuration parameters and their values. In case the user supplies a
name from the command line, that name is used. The file is expected to
contain one parameter per line, with the name of the parameter in column
one and the value in column two.
- The function 'HandleGET' reflects the structure of the menu tree as
+ The function 'HandleGET()' reflects the structure of the menu tree as
usual. The first menu choice tells the user what this is all about.
The second choice reads the configuration file line by line and stores
the parameters and their values. Notice that the record separator for
@@ -2223,12 +2223,12 @@ those lines that differ in their second and third
columns:
Another thing that may look strange is the way GETURL is called.
Before calling GETURL, we have to check if the proxy variables need to
be passed on. If so, we prepare strings that will become part of the
-command line later. In 'GetHeader', we store these strings together
+command line later. In 'GetHeader()', we store these strings together
with the longest part of the command line. Later, in the loop over the
-URLs, 'GetHeader' is appended with the URL and a redirection operator to
-form the command that reads the URL's header over the Internet. GETURL
-always produces the headers over '/dev/stderr'. That is the reason why
-we need the redirection operator to have the header piped in.
+URLs, 'GetHeader()' is appended with the URL and a redirection operator
+to form the command that reads the URL's header over the Internet.
+GETURL always produces the headers over '/dev/stderr'. That is the
+reason why we need the redirection operator to have the header piped in.
This program is not perfect because it assumes that changing URLs
results in changed lengths, which is not necessarily true. A more
@@ -2268,7 +2268,7 @@ record separators. With 'RS' set to a regular expression
that matches
links, the second action is executed each time a non-empty link is
found. We can find the matching link itself in 'RT'.
- The action could use the 'system' function to let another GETURL
+ The action could use the 'system()' function to let another GETURL
retrieve the page, but here we use a different approach. This simple
program prints shell commands that can be piped into 'sh' for execution.
This way it is possible to first extract the links, wrap shell commands
@@ -2346,14 +2346,14 @@ an image of the distributions. The statistical
computation follows
'Numerical Recipes in C: The Art of Scientific Computing' by William H.
Press, Saul A. Teukolsky, William T. Vetterling, and Brian P. Flannery.
Since 'gawk' does not have a built-in function for the computation of
-the beta function, we use the 'ibeta' function of GNUPlot. As a side
+the beta function, we use the 'ibeta()' function of GNUPlot. As a side
effect, we learn how to use GNUPlot as a sophisticated calculator. The
comparison of means is done as in 'tutest', paragraph 14.2, page 613,
and the comparison of variances is done as in 'ftest', page 611 in
'Numerical Recipes'.
As usual, we take the site-independent code for servers and append
-our own functions 'SetUpServer' and 'HandleGET':
+our own functions 'SetUpServer()' and 'HandleGET()':
function SetUpServer() {
TopHeader = "<HTML><title>Statistics with GAWK</title>"
@@ -2369,7 +2369,7 @@ our own functions 'SetUpServer' and 'HandleGET':
}
Here, you see the menu structure that the user sees. Later, we will
-see how the program structure of the 'HandleGET' function reflects the
+see how the program structure of the 'HandleGET()' function reflects the
menu structure. What is missing here is the link for the image we
generate. In an event-driven environment, request, generation, and
delivery of images are separated.
@@ -2382,7 +2382,7 @@ output, enabling us to read results of calculations with
'getline'. By
initializing the statistical parameters with some meaningful defaults,
we make sure the user gets an image the first time he uses the program.
- Following is the rather long function 'HandleGET', which implements
+ Following is the rather long function 'HandleGET()', which implements
the contents of this service by reacting to the different kinds of
requests from the browser. Before you start playing with this script,
make sure that your browser supports JavaScript and that it also has
@@ -2500,9 +2500,9 @@ the server should be ready for serving the next request.
But there is one more subtlety in the JavaScript code. Each time the
JavaScript code opens a window for the image, the name of the image is
-appended with a timestamp ('systime'). Why this constant change of name
-for the image? Initially, we always named the image 'Image', but then
-the Netscape browser noticed the name had _not_ changed since the
+appended with a timestamp ('systime()'). Why this constant change of
+name for the image? Initially, we always named the image 'Image', but
+then the Netscape browser noticed the name had _not_ changed since the
previous request and displayed the previous image (caching behavior).
The server core is implemented so that browsers are told _not_ to cache
anything. Obviously HTTP requests do not always work as expected. One
@@ -2579,10 +2579,10 @@ those boring 'Hello world' examples here, that are
usually presented
when introducing novices to VRML. If you have never written any VRML
code, have a look at the VRML FAQ. Presenting a static VRML scene is a
bit trivial; in order to expose 'gawk''s new capabilities, we will
-present a dynamically generated VRML scene. The function 'SetUpServer'
-is very simple because it only sets the default HTML page and
-initializes the random number generator. As usual, the surrounding
-server lets you browse the maze.
+present a dynamically generated VRML scene. The function
+'SetUpServer()' is very simple because it only sets the default HTML
+page and initializes the random number generator. As usual, the
+surrounding server lets you browse the maze.
function SetUpServer() {
TopHeader = "<HTML><title>Walk through a maze</title>"
@@ -2596,14 +2596,14 @@ server lets you browse the maze.
srand()
}
- The function 'HandleGET' is a bit longer because it first computes
+ The function 'HandleGET()' is a bit longer because it first computes
the maze and afterwards generates the VRML code that is sent across the
network. As shown in the STATIST example (*note STATIST::), we set the
type of the content to VRML and then store the VRML representation of
the maze as the page content. We assume that the maze is stored in a 2D
array. Initially, the maze consists of walls only. Then, we add an
entry and an exit to the maze and let the rest of the work be done by
-the function 'MakeMaze'. Now, only the wall fields are left in the
+the function 'MakeMaze()'. Now, only the wall fields are left in the
maze. By iterating over the these fields, we generate one line of VRML
code for each wall field.
@@ -2653,7 +2653,7 @@ code for each wall field.
}
}
- Finally, we have a look at 'MakeMaze', the function that generates
+ Finally, we have a look at 'MakeMaze()', the function that generates
the 'Maze' array. When entered, this function assumes that the array
has been initialized so that each element represents a wall element and
the maze is initially full of wall elements. Only the entrance and the
@@ -2862,34 +2862,34 @@ mobile agent:
close(HttpService)
}
- The 'migrate' function prepares the aforementioned strings containing
-the program code and transmits them to a server. A consequence of this
-modular approach is that the 'migrate' function takes some parameters
-that aren't needed in this application, but that will be in future ones.
-Its mandatory parameter 'Destination' holds the name (or IP address) of
-the server that the agent wants as a host for its code. The optional
-parameter 'MobCode' may contain some 'gawk' code that is inserted during
-migration in front of all other code. The optional parameter 'Label'
-may contain a string that tells the agent what to do in program
-execution after arrival at its new home site. One of the serious
-obstacles in implementing a framework for mobile agents is that it does
-not suffice to migrate the code. It is also necessary to migrate the
-state of execution of the agent. In contrast to 'Agent Tcl', this
-program does not try to migrate the complete set of variables. The
-following conventions are used:
+ The 'migrate()' function prepares the aforementioned strings
+containing the program code and transmits them to a server. A
+consequence of this modular approach is that the 'migrate()' function
+takes some parameters that aren't needed in this application, but that
+will be in future ones. Its mandatory parameter 'Destination' holds the
+name (or IP address) of the server that the agent wants as a host for
+its code. The optional parameter 'MobCode' may contain some 'gawk' code
+that is inserted during migration in front of all other code. The
+optional parameter 'Label' may contain a string that tells the agent
+what to do in program execution after arrival at its new home site. One
+of the serious obstacles in implementing a framework for mobile agents
+is that it does not suffice to migrate the code. It is also necessary
+to migrate the state of execution of the agent. In contrast to 'Agent
+Tcl', this program does not try to migrate the complete set of
+variables. The following conventions are used:
* Each variable in an agent program is local to the current host and
does _not_ migrate.
* The array 'MOBFUN' shown above is an exception. It is handled by
- the function 'migrate' and does migrate with the application.
+ the function 'migrate()' and does migrate with the application.
* The other exception is the array 'MOBVAR'. Each variable that
takes part in migration has to be an element of this array.
- 'migrate' also takes care of this.
+ 'migrate()' also takes care of this.
Now it's clear what happens to the 'Label' parameter of the function
-'migrate'. It is copied into 'MOBVAR["Label"]' and travels alongside
+'migrate()'. It is copied into 'MOBVAR["Label"]' and travels alongside
the other data. Since travelling takes place via HTTP, records must be
separated with '"\r\n"' in 'RS' and 'ORS' as usual. The code assembly
for migration takes place in three steps:
@@ -2908,8 +2908,8 @@ for migration takes place in three steps:
follows is the 'END' pattern that is executed when the mobile agent has
finished reading its own code. First, it checks whether it is already
running on a remote host or not. In case initialization has not yet
-taken place, it starts 'MyInit'. Otherwise (later, on a remote host),
-it starts 'MyJob':
+taken place, it starts 'MyInit()'. Otherwise (later, on a remote host),
+it starts 'MyJob()':
END {
if (ARGC != 2) exit # stop when called with wrong parameters
@@ -2920,9 +2920,9 @@ it starts 'MyJob':
}
All that's left to extend the framework into a complete application
-is to write two application-specific functions: 'MyInit' and 'MyJob'.
-Keep in mind that the former is executed once on the originating host,
-while the latter is executed after each migration:
+is to write two application-specific functions: 'MyInit()' and
+'MyJob()'. Keep in mind that the former is executed once on the
+originating host, while the latter is executed after each migration:
function MyInit() {
MOBVAR["MyOrigin"] = MyOrigin
@@ -2938,8 +2938,8 @@ while the latter is executed after each migration:
('MyOrigin') with it. Then, it takes the name of its first destination
and goes there for further work. Notice that this name has the port
number of the web server appended to the name of the server, because the
-function 'migrate' needs it this way to create the 'HttpService'
-variable. Finally, it waits for the result to arrive. The 'MyJob'
+function 'migrate()' needs it this way to create the 'HttpService'
+variable. Finally, it waits for the result to arrive. The 'MyJob()'
function runs on the remote host:
function MyJob() {
@@ -2959,7 +2959,7 @@ function runs on the remote host:
}
}
- After migrating, the first thing to do in 'MyJob' is to delete the
+ After migrating, the first thing to do in 'MyJob()' is to delete the
name of the current host from the list of hosts to visit. Now, it is
time to start the real work by appending the host's name to the result
string, and reading line by line who is logged in on this host. A very
@@ -3071,7 +3071,7 @@ structure of the script is as follows:
}
The earlier parts store data into variables and arrays which are
-subsequently used by later parts of the script. The 'Init' function
+subsequently used by later parts of the script. The 'Init()' function
first checks if the script is invoked correctly (without any
parameters). If not, it informs the user of the correct usage. What
follows are preparations for the retrieval of the historical quote data.
@@ -3229,7 +3229,7 @@ could have made in the year before.
At this point the hard work has been done: the array 'predict'
contains the predictions for all the ticker symbols. It is up to the
-function 'Report' to find some nice words to introduce the desired
+function 'Report()' to find some nice words to introduce the desired
information.
function Report() {
@@ -3266,9 +3266,9 @@ information.
report = report "you should visit a doctor who can treat your ailment."
}
- The function 'SendMail' goes through the list of customers and opens
-a pipe to the 'mail' command for each of them. Each one receives an
-email message with a proper subject heading and is addressed with his
+ The function 'SendMail()' goes through the list of customers and
+opens a pipe to the 'mail' command for each of them. Each one receives
+an email message with a proper subject heading and is addressed with his
full name.
function SendMail() {
@@ -4288,6 +4288,13 @@ Index
* record separators, POP and: Email. (line 36)
* REMCONF program: REMCONF. (line 6)
* remoteport field: Gawk Special Files. (line 34)
+* RFC 1939: Email. (line 6)
+* RFC 1939 <1>: Email. (line 36)
+* RFC 1945: Web page. (line 29)
+* RFC 2068: Web page. (line 6)
+* RFC 2068 <1>: Interacting Service. (line 104)
+* RFC 2616: Web page. (line 6)
+* RFC 821: Email. (line 6)
* robot: Challenges. (line 84)
* robot <1>: WEBGRAB. (line 6)
* RS variable, HTTP and: Web page. (line 29)
@@ -4367,33 +4374,33 @@ Node: TCP Connecting30827
Node: Troubleshooting33173
Ref: Troubleshooting-Footnote-136232
Node: Interacting36805
-Node: Setting Up39543
-Node: Email43046
-Node: Web page45378
-Ref: Web page-Footnote-148195
-Node: Primitive Service48393
-Node: Interacting Service51134
-Ref: Interacting Service-Footnote-160291
-Node: CGI Lib60323
-Node: Simple Server67287
-Ref: Simple Server-Footnote-175016
-Node: Caveats75117
-Node: Challenges76262
-Node: Some Applications and Techniques84960
-Node: PANIC87421
-Node: GETURL89145
-Node: REMCONF91778
-Node: URLCHK97265
-Node: WEBGRAB101114
-Node: STATIST105574
-Ref: STATIST-Footnote-1117311
-Node: MAZE117756
-Node: MOBAGWHO123955
-Ref: MOBAGWHO-Footnote-1137947
-Node: STOXPRED138002
-Node: PROTBASE152284
-Node: Links165400
-Node: GNU Free Documentation License168833
-Node: Index193953
+Node: Setting Up39545
+Node: Email43048
+Node: Web page45380
+Ref: Web page-Footnote-148197
+Node: Primitive Service48395
+Node: Interacting Service51136
+Ref: Interacting Service-Footnote-160303
+Node: CGI Lib60335
+Node: Simple Server67310
+Ref: Simple Server-Footnote-175053
+Node: Caveats75154
+Node: Challenges76299
+Node: Some Applications and Techniques84997
+Node: PANIC87462
+Node: GETURL89186
+Node: REMCONF91819
+Node: URLCHK97314
+Node: WEBGRAB101166
+Node: STATIST105628
+Ref: STATIST-Footnote-1117377
+Node: MAZE117822
+Node: MOBAGWHO124029
+Ref: MOBAGWHO-Footnote-1138047
+Node: STOXPRED138102
+Node: PROTBASE152390
+Node: Links165506
+Node: GNU Free Documentation License168939
+Node: Index194059
End Tag Table
diff --git a/doc/gawkinet.texi b/doc/gawkinet.texi
index 94f5f49..5433462 100644
--- a/doc/gawkinet.texi
+++ b/doc/gawkinet.texi
@@ -67,7 +67,7 @@
@set TITLE TCP/IP Internetworking with @command{gawk}
@set EDITION 1.4
address@hidden UPDATE-MONTH March, 2016
address@hidden UPDATE-MONTH April, 2016
@c gawk versions:
@set VERSION 4.1
@set PATCHLEVEL 4
@@ -961,32 +961,6 @@ connects to other services that should give you some
response. If you are
curious, you should have a look at your @file{/etc/services} file. It could
look like this:
address@hidden
address@hidden {1234567890123} {1234567890123}
{123456789012345678901234567890123456789012}
address@hidden Service @strong{name} @tab Service @strong{number}
address@hidden echo @tab 7/tcp @tab echo sends back each line it receives
address@hidden echo @tab 7/udp @tab echo is good for testing purposes
address@hidden discard @tab 9/tcp @tab discard behaves like @file{/dev/null}
address@hidden discard @tab 9/udp @tab discard just throws away each line
address@hidden daytime @tab 13/tcp @tab daytime sends date & time once per
connection
address@hidden daytime @tab 13/udp
address@hidden chargen @tab 19/tcp @tab chargen infinitely produces character
sets
address@hidden chargen @tab 19/udp @tab chargen is good for testing purposes
address@hidden ftp @tab 21/tcp @tab ftp is the usual file transfer protocol
address@hidden telnet @tab 23/tcp @tab telnet is the usual login facility
address@hidden smtp @tab 25/tcp @tab smtp is the Simple Mail Transfer Protocol
address@hidden finger @tab 79/tcp @tab finger tells you who is logged in
address@hidden www @tab 80/tcp @tab www is the HyperText Transfer Protocol
address@hidden pop2 @tab 109/tcp @tab pop2 is an older version of pop3
address@hidden pop2 @tab 109/udp
address@hidden pop3 @tab 110/tcp @tab pop3 is the Post Office Protocol
address@hidden pop3 @tab 110/udp @tab pop3 is used for receiving email
address@hidden nntp @tab 119/tcp @tab nntp is the USENET News Transfer Protocol
address@hidden irc @tab 194/tcp @tab irc is the Internet Relay Chat
address@hidden irc @tab 194/udp
address@hidden multitable
address@hidden ignore
-
@smallexample
# /etc/services:
#
@@ -1076,7 +1050,7 @@ of all users currently logged in, replace @var{name} with
an empty string
@cindex Linux
@cindex GNU/Linux
-The final @code{close} command could be safely deleted from
+The final @code{close()} command could be safely deleted from
the above script, because the operating system closes any open connection
by default when a script reaches the end of execution. In order to avoid
portability problems, it is best to always close connections explicitly.
@@ -1084,59 +1058,6 @@ With the Linux kernel,
for example, proper closing results in flushing of buffers. Letting
the close happen by default may result in discarding buffers.
address@hidden
address@hidden Chuck comments that this seems out of place. He's right. I
dunno
address@hidden where to put it though.
address@hidden @command{finger} utility
address@hidden RFC 1288
-In the early days of the Internet (up until about 1992), you could use
-such a program to check if some user in another country was logged in on
-a specific machine.
-RFC address@hidden@uref{http://www.cis.ohio-state.edu/htbin/rfc/rfc1288.html}}
-provides the exact definition of the @command{finger} protocol.
-Every contemporary Unix system also has a command named @command{finger},
-which functions as a client for the protocol of the same name.
-Still today, some people maintain simple information systems
-with this ancient protocol. For example, by typing
address@hidden quake@@seismo.unr.edu}
-you get the latest @dfn{Earthquake Bulletin} for the state of Nevada.
-
address@hidden Earthquake Bulletin
address@hidden
-$ finger quake@@seismo.unr.edu
-
address@hidden
-
-DATE-(UTC)-TIME LAT LON DEP MAG COMMENTS
-yy/mm/dd hh:mm:ss deg. deg. km
-
-98/12/14 21:09:22 37.47N 116.30W 0.0 2.3Md 76.4 km S of WARM SPRINGS,
NEVA
-98/12/14 22:05:09 39.69N 120.41W 11.9 2.1Md 53.8 km WNW of RENO, NEVADA
-98/12/15 14:14:19 38.04N 118.60W 2.0 2.3Md 51.0 km S of HAWTHORNE, NEVADA
-98/12/17 01:49:02 36.06N 117.58W 13.9 3.0Md 74.9 km SE of LONE PINE,
CALIFOR
-98/12/17 05:39:26 39.95N 120.87W 6.2 2.6Md 101.6 km WNW of RENO, NEVADA
-98/12/22 06:07:42 38.68N 119.82W 5.2 2.3Md 50.7 km S of CARSON CITY,
NEVAD
address@hidden smallexample
-
address@hidden
-This output from @command{finger} contains the time, location, depth,
-magnitude, and a short comment about
-the earthquakes registered in that region during the last 10 days.
-In many places today the use of such services is restricted
-because most networks have firewalls and proxy servers between them
-and the Internet. Most firewalls are programmed to not let
address@hidden requests go beyond the local network.
-
address@hidden Coke machine
-Another (ab)use of the @command{finger} protocol are several Coke machines
-that are connected to the Internet. There is a short list of such
-Coke
address@hidden@uref{http://ca.yahoo.com/Computers_and_Internet/Internet/Devices_Connected_to_the_Internet/Soda_Machines/}}
-You can access them either from the command-line or with a simple
address@hidden script. They usually tell you about the different
-flavors of Coke and beer available there. If you have an account there,
-you can even order some drink this way.
address@hidden ignore
-
When looking at @file{/etc/services} you may have noticed that the
@samp{daytime} service is also available with @samp{udp}. In the earlier
example, change @samp{tcp} to @samp{udp},
@@ -1258,8 +1179,8 @@ execute arbitrary commands, anyone would be free to do
@samp{rm -rf *}.
@node Email, Web page, Setting Up, Using Networking
@section Reading Email
address@hidden @cindex RFC 1939
address@hidden @cindex RFC 821
address@hidden RFC 1939
address@hidden RFC 821
@cindex @command{gawk}, networking, See Also email
@cindex networks, @command{gawk} and, See Also email
@cindex POP (Post Office Protocol)
@@ -1270,11 +1191,6 @@ The distribution of email is usually done by dedicated
email servers that
communicate with your machine using special protocols. To receive email, we
will use the Post Office Protocol (POP). Sending can be done with the much
older Simple Mail Transfer Protocol (SMTP).
address@hidden
address@hidden 1939 defines POP.
-RFC 821 defines SMTP. See
address@hidden://rfc.fh-koeln.de/doc/rfc/html/rfc.html, RFCs in HTML}.}
address@hidden ignore
@cindex email
When you type in the following program, replace the @var{emailhost} by the
@@ -1304,7 +1220,7 @@ BEGIN @{
@}
@end example
address@hidden @cindex RFC 1939
address@hidden RFC 1939
@cindex record separators, POP and
@cindex @code{RS} variable, POP and
@cindex @code{ORS} variable, POP and
@@ -1328,8 +1244,8 @@ message it reads, but instead leaves it on the server.
@cindex web pages
@cindex HTTP (Hypertext Transfer Protocol)
@cindex Hypertext Transfer Protocol, See HTTP
address@hidden @cindex RFC 2068
address@hidden @cindex RFC 2616
address@hidden RFC 2068
address@hidden RFC 2616
Retrieving a web page from a web server is as simple as
retrieving email from an email server. We only have to use a
@@ -1339,41 +1255,6 @@ protocol is HyperText Transfer Protocol (HTTP) and the
port number is usually
name of your local web server or proxy web server and its port number
for HTTP requests.
address@hidden
address@hidden Chuck says this stuff isn't necessary
-More detailed information about HTTP can be found at
-the home of the web protocols,@address@hidden://www.w3.org/pub/WWW/Protocols}}
-including the specification of HTTP in RFC 2068. The protocol specification
-in RFC 2068 is concise and you can get it for free. If you need more
-explanation and you are willing to pay for a book, you might be
-interested in one of these books:
-
address@hidden
-
address@hidden
-When we started writing web clients and servers with @command{gawk},
-the only book available with details about HTTP was the one by Paul Hethmon
-called
address@hidden Guide to
address@hidden@uref{http://www.browsebooks.com/Hethmon/?882}}
-Hethmon not only describes HTTP,
-he also implements a simple web server in C++.
-
address@hidden
-Since July 2000, O'Reilly offers the book by Clinton Wong called
address@hidden Pocket
address@hidden@uref{http://www.oreilly.com/catalog/httppr}}
-It only has 75 pages but its
-focus definitely is HTTP. This pocket reference is not a replacement
-for the RFC, but I wish I had had it back in 1997 when I started writing
-scripts to handle HTTP.
-
address@hidden
-Another small booklet about HTTP is the one by Toexcell Incorporated Staff,
-ISBN 1-58348-270-9, called
address@hidden Transfer Protocol Http 1.0 Specifications}
-
address@hidden enumerate
address@hidden ignore
-
The following program employs a rather crude approach toward retrieving a
web page. It uses the prehistoric syntax of HTTP 0.9, which almost all
web servers still support. The most noticeable thing about it is that the
@@ -1391,7 +1272,7 @@ BEGIN @{
@}
@end example
address@hidden @cindex RFC 1945
address@hidden RFC 1945
@cindex record separators, HTTP and
@cindex @code{RS} variable, HTTP and
@cindex @code{ORS} variable, HTTP and
@@ -1439,17 +1320,6 @@ print get |& HttpService
@end example
You can also request weather reports this way.
address@hidden
address@hidden Boutell, Thomas
-A good book to go on with is
-the
address@hidden Source
address@hidden@uref{http://www.utoronto.ca/webdocs/HTMLdocs/NewHTML/book.html}}
-There are also some books on CGI programming
-like @cite{CGI Programming in C & Perl},
-by Thomas
address@hidden@uref{http://cseng.aw.com/bookdetail.qry?ISBN=0-201-42219-0&ptype=0}},
-and @cite{The CGI address@hidden@uref{http://www.cgibook.com}}
-Another good source is @cite{The CGI Resource
address@hidden@uref{http://www.cgi-resources.com}}
address@hidden ignore
@node Primitive Service, Interacting Service, Web page, Using Networking
@section A Primitive Web Service
@@ -1606,7 +1476,7 @@ HTML content of the web pages to refer to the home system.
Each server that is built around this core has to initialize some
application-dependent variables (such as the default home page) in a procedure
address@hidden, which is called immediately before entering the
address@hidden()}, which is called immediately before entering the
infinite loop of the server. For now, we will write an instance that
initiates a trivial interaction. With this home page, the client user
can click on two possible choices, and receive the current date either
@@ -1631,7 +1501,7 @@ is the first run, @code{GETARG["Method"]} is not
initialized yet, hence the
case selection over the method does nothing. Now that the home page is
initialized, the server can start communicating to a client browser.
address@hidden @cindex RFC 2068
address@hidden RFC 2068
It does so by printing the HTTP header into the network connection
(@samp{print @dots{} |& HttpService}). This command blocks execution of
the server script until a client connects. If this server
@@ -1648,12 +1518,12 @@ Having supplied the initial home page to the browser
with a valid document
stored in the parameter @code{Prompt}, it closes the connection and waits
for the next request. When the request comes, a log line is printed that
allows us to see which request the server receives. The final step in the
-loop is to call the function @code{CGI_setup}, which reads all the lines
+loop is to call the function @code{CGI_setup()}, which reads all the lines
of the request (coming from the browser), processes them, and stores the
transmitted parameters in the array @code{PARAM}. The complete
text of these application-independent functions can be found in
@ref{CGI Lib, ,A Simple CGI Library}.
-For now, we use a simplified version of @code{CGI_setup}:
+For now, we use a simplified version of @code{CGI_setup()}:
@example
function CGI_setup( method, uri, version, i) @{
@@ -1700,7 +1570,7 @@ array as well as the body.
On each subsequent run through the main loop, one request from a browser is
received, evaluated, and answered according to the user's choice. This can be
done by letting the value of the HTTP method guide the main loop into
-execution of the procedure @code{HandleGET}, which evaluates the user's
+execution of the procedure @code{HandleGET()}, which evaluates the user's
choice. In this case, we have only one hierarchical level of menus,
but in the general case,
menus are nested.
@@ -1738,7 +1608,7 @@ which may contain only
monochrome pictures but is an ASCII format. Binary images are possible but
not so easy to handle. Another way of including images is to generate them
with a tool such as GNUPlot,
-by calling the tool with the @code{system} function or through a pipe.
+by calling the tool with the @code{system()} function or through a pipe.
@node CGI Lib, , Interacting Service, Interacting Service
@subsection A Simple CGI Library
@@ -1752,7 +1622,7 @@ Phil Smith III,@*
@c STARTOFRANGE cgilib
@cindex CGI (Common Gateway Interface), library
In @ref{Interacting Service, ,A Web Service with Interaction},
-we saw the function @code{CGI_setup} as part of the web server
+we saw the function @code{CGI_setup()} as part of the web server
``core logic'' framework. The code presented there handles almost
everything necessary for CGI requests.
One thing it doesn't do is handle encoded characters in the requests.
@@ -1875,9 +1745,9 @@ function CGI_setup( method, uri, version, i)
@c endfile
@end example
-This isolates details in a single function, @code{CGI_setup}.
+This isolates details in a single function, @code{CGI_setup()}.
Decoding of encoded characters is pushed off to a helper function,
address@hidden The use of the leading underscore (@samp{_}) in
address@hidden()}. The use of the leading underscore (@samp{_}) in
the function name is intended to indicate that it is an ``internal''
function, although there is nothing to enforce this:
@@ -1916,9 +1786,9 @@ function _CGI_decode(str, hexdigs, i, pre, code1, code2,
This works by splitting the string apart around an encoded character.
The two digits are converted to lowercase characters and looked up in a string
of hex digits. Note that @code{0} is not in the string on purpose;
address@hidden returns zero when it's not found, automatically giving
address@hidden()} returns zero when it's not found, automatically giving
the correct value! Once the hexadecimal value is converted from
-characters in a string into a numerical value, @code{sprintf}
+characters in a string into a numerical value, @code{sprintf()}
converts the value back into a real character.
The following is a simple test harness for the above functions:
@@ -2007,22 +1877,22 @@ function SetUpServer() @{
@c endfile
@end example
address@hidden is similar to the previous example,
-except for calling another function, @code{SetUpEliza}.
address@hidden()} is similar to the previous example,
+except for calling another function, @code{SetUpEliza()}.
This approach can be used to implement other kinds of servers.
The only changes needed to do so are hidden in the functions
address@hidden and @code{HandleGET}. Perhaps it might be necessary to
address@hidden()} and @code{HandleGET()}. Perhaps it might be necessary to
implement other HTTP methods.
The @command{igawk} program that comes with @command{gawk}
may be useful for this process.
When extending this example to a complete application, the first
-thing to do is to implement the function @code{SetUpServer} to
+thing to do is to implement the function @code{SetUpServer()} to
initialize the HTML pages and some variables. These initializations
determine the way your HTML pages look (colors, titles, menu
items, etc.).
-The function @code{HandleGET} is a nested case selection that decides
+The function @code{HandleGET()} is a nested case selection that decides
which page the user wants to see next. Each nesting level refers to a menu
level of the GUI. Each case implements a certain action of the menu. On the
deepest level of case selection, the handler essentially knows what the
@@ -2119,7 +1989,7 @@ function ElizaSays(YouSay) @{
@c endfile
@end smallexample
-In the long but simple function @code{SetUpEliza}, you can see tables
+In the long but simple function @code{SetUpEliza()}, you can see tables
for conjugation, keywords, and address@hidden version shown
here is abbreviated. The full version comes with the @command{gawk}
distribution.} The associative array @code{k}
@@ -2537,7 +2407,7 @@ we built in
@ref{Simple Server, ,A Simple Web Server}.
When building new and nontrivial servers, we
always copy this building block and append new instances of the two
-functions @code{SetUpServer} and @code{HandleGET}.
+functions @code{SetUpServer()} and @code{HandleGET()}.
This makes a lot of sense, since
this scheme of event-driven
@@ -2716,7 +2586,7 @@ process in the embedded system may read the file. The
program uses the
site-independent part of the simple web server that we developed in
@ref{Interacting Service, ,A Web Service with Interaction}.
As mentioned there, all we have to do is to write two new procedures
address@hidden and @code{HandleGET}:
address@hidden()} and @code{HandleGET()}:
@smallexample
@c file eg/network/remconf.awk
@@ -2737,14 +2607,14 @@ function SetUpServer() @{
@c endfile
@end smallexample
-The function @code{SetUpServer} initializes the top level HTML texts
+The function @code{SetUpServer()} initializes the top level HTML texts
as usual. It also initializes the name of the file that contains the
configuration parameters and their values. In case the user supplies
a name from the command line, that name is used. The file is expected to
contain one parameter per line, with the name of the parameter in
column one and the value in column two.
-The function @code{HandleGET} reflects the structure of the menu
+The function @code{HandleGET()} reflects the structure of the menu
tree as usual. The first menu choice tells the user what this is all
about. The second choice reads the configuration file line by line
and stores the parameters and their values. Notice that the record
@@ -2884,9 +2754,9 @@ BEGIN @{
Another thing that may look strange is the way GETURL is called.
Before calling GETURL, we have to check if the proxy variables need
to be passed on. If so, we prepare strings that will become part
-of the command line later. In @code{GetHeader}, we store these strings
+of the command line later. In @code{GetHeader()}, we store these strings
together with the longest part of the command line. Later, in the loop
-over the URLs, @code{GetHeader} is appended with the URL and a redirection
+over the URLs, @code{GetHeader()} is appended with the URL and a redirection
operator to form the command that reads the URL's header over the Internet.
GETURL always produces the headers over @file{/dev/stderr}. That is
the reason why we need the redirection operator to have the header
@@ -2933,7 +2803,7 @@ separators. With @code{RS} set to a regular expression
that matches links,
the second action is executed each time a non-empty link is found.
We can find the matching link itself in @code{RT}.
-The action could use the @code{system} function to let another GETURL
+The action could use the @code{system()} function to let another GETURL
retrieve the page, but here we use a different approach.
This simple program prints shell commands that can be piped into @command{sh}
for execution. This way it is possible to first extract
@@ -3044,7 +2914,7 @@ distributions. The statistical computation follows
@cite{Numerical Recipes in C: The Art of Scientific Computing}
by William H.@: Press, Saul A.@: Teukolsky, William T.@: Vetterling, and Brian
P. Flannery.
Since @command{gawk} does not have a built-in function
-for the computation of the beta function, we use the @code{ibeta} function
+for the computation of the beta function, we use the @code{ibeta()} function
of GNUPlot. As a side effect, we learn how to use GNUPlot as a
sophisticated calculator. The comparison of means is done as in @code{tutest},
paragraph 14.2, page 613, and the comparison of variances is done as in
@code{ftest},
@@ -3052,7 +2922,7 @@ page 611 in @cite{Numerical Recipes}.
@cindex Numerical Recipes
As usual, we take the site-independent code for servers and append
-our own functions @code{SetUpServer} and @code{HandleGET}:
+our own functions @code{SetUpServer()} and @code{HandleGET()}:
@smallexample
@c file eg/network/statist.awk
@@ -3072,7 +2942,7 @@ function SetUpServer() @{
@end smallexample
Here, you see the menu structure that the user sees. Later, we
-will see how the program structure of the @code{HandleGET} function
+will see how the program structure of the @code{HandleGET()} function
reflects the menu structure. What is missing here is the link for the
image we generate. In an event-driven environment, request,
generation, and delivery of images are separated.
@@ -3088,7 +2958,7 @@ defaults, we make sure the user gets an image the first
time
he uses the program.
@cindex JavaScript
-Following is the rather long function @code{HandleGET}, which
+Following is the rather long function @code{HandleGET()}, which
implements the contents of this service by reacting to the different
kinds of requests from the browser. Before you start playing with
this script, make sure that your browser supports JavaScript and that it also
@@ -3212,7 +3082,7 @@ By this time, the server should be ready for serving the
next request.
But there is one more subtlety in the JavaScript code.
Each time the JavaScript code opens a window for the image, the
-name of the image is appended with a timestamp (@code{systime}).
+name of the image is appended with a timestamp (@code{systime()}).
Why this constant change of name for the image? Initially, we always named
the image @code{Image}, but then the Netscape browser noticed the name
had @emph{not} changed since the previous request and displayed the
@@ -3289,7 +3159,7 @@ any VRML code, have a look at
the VRML FAQ.
Presenting a static VRML scene is a bit trivial; in order to expose
@command{gawk}'s new capabilities, we will present a dynamically generated
-VRML scene. The function @code{SetUpServer} is very simple because it
+VRML scene. The function @code{SetUpServer()} is very simple because it
only sets the default HTML page and initializes the random number
generator. As usual, the surrounding server lets you browse the maze.
@@ -3309,7 +3179,7 @@ function SetUpServer() @{
@c endfile
@end smallexample
-The function @code{HandleGET} is a bit longer because it first computes
+The function @code{HandleGET()} is a bit longer because it first computes
the maze and afterwards generates the VRML code that is sent across
the network. As shown in the STATIST example
(@pxref{STATIST}),
@@ -3317,7 +3187,7 @@ we set the type of the
content to VRML and then store the VRML representation of the maze as the
page content. We assume that the maze is stored in a 2D array. Initially,
the maze consists of walls only. Then, we add an entry and an exit to the
-maze and let the rest of the work be done by the function @code{MakeMaze}.
+maze and let the rest of the work be done by the function @code{MakeMaze()}.
Now, only the wall fields are left in the maze. By iterating over the these
fields, we generate one line of VRML code for each wall field.
@@ -3371,7 +3241,7 @@ Group @{\n\
@c endfile
@end smallexample
-Finally, we have a look at @code{MakeMaze}, the function that generates
+Finally, we have a look at @code{MakeMaze()}, the function that generates
the @code{Maze} array. When entered, this function assumes that the array
has been initialized so that each element represents a wall element and
the maze is initially full of wall elements. Only the entrance and the exit
@@ -3440,94 +3310,6 @@ the networking world. For an unbiased view at this
technology,
see the remarkable paper @cite{Mobile Agents: Are they a good
address@hidden@uref{http://www.research.ibm.com/massive/mobag.ps}}
address@hidden
address@hidden Chuck says to take all of this out.
address@hidden Tcl/Tk
-A good instance of this paradigm is
address@hidden
Tcl},@address@hidden://agent.cs.dartmouth.edu/software/agent2.0/}}
-an extension of the Tcl language. After introducing a typical
-development environment, the aforementioned paper shows a nice little
-example application that we will try to rebuild in @command{gawk}. The
address@hidden agent takes a list of servers and wanders from one server
-to the next one, always looking to see who is logged in.
-Having reached the last
-one, it sends back a message with a list of all users it found on each
-machine.
-
-But before implementing something that might or might not be a mobile
-agent, let us clarify the concept and some important terms. The agent
-paradigm in general is such a young scientific discipline that it has
-not yet developed a widely-accepted terminology. Some authors try to
-give precise definitions, but their scope is often not wide enough
-to be generally accepted. Franklin and Graesser ask
address@hidden it an Agent or just a Program: A Taxonomy for Autonomous
address@hidden@uref{http://www.msci.memphis.edu/~franklin/AgentProg.html}}
-and give even better answers than Caglayan and Harrison in their
address@hidden address@hidden@uref{http://www.aminda.com/mazzu/sourcebook/}}
-
address@hidden @minus
address@hidden
address@hidden autonomous agent is a system situated within and a part of
-an environment that senses that environment and acts on it, over time, in
-pursuit of its own agenda and so as to effect what it senses in the future.}
-(Quoted from Franklin and Graesser.)
address@hidden
-A mobile agent is able to transport itself from one machine to another.
address@hidden
-The term @dfn{migration} often denotes this process of moving.
-But neither of the two sources above even mentions this term, while others
-use it regularly.
address@hidden itemize
-
-Before delving into the (rather demanding) details of
-implementation, let us give just one more quotation as a final
-motivation. Steven Farley published an excellent paper called
address@hidden Agent System Architecture},@footnote{This often
-cited text originally appeared as a conference paper here:
address@hidden://www.sigs.com/publications/docs/java/9705/farley.html}
-Many bibliographies on the Internet point to this dead link. Meanwhile,
-the paper appeared as a contribution to a book called More Java Gems here:
address@hidden://uk.cambridge.org/computerscience/object/catalogue/0521774772/default.htm}}
-in which he asks ``Why use an agent architecture?''
-
address@hidden
-If client-server systems are the currently established norm and distributed
-object systems such as CORBA are defining the future standards, why bother
-with agents? Agent architectures have certain advantages over these other
-types. Three of the most important advantages are:
address@hidden CORBA
-
address@hidden
address@hidden
-An agent performs much processing at the server where local bandwidth
-is high, thus reducing the amount of network bandwidth consumed and increasing
-overall performance. In contrast, a CORBA client object with the equivalent
-functionality of a given agent must make repeated remote method calls to
-the server object because CORBA objects cannot move across the network
-at runtime.
-
address@hidden
-An agent operates independently of the application from which the
-agent was invoked. The agent operates asynchronously, meaning that the
-client application does not need to wait for the results. This is especially
-important for mobile users who are not always connected to the network.
-
address@hidden
-The use of agents allows for the injection of new functionality into
-a system at run time. An agent system essentially contains its own automatic
-software distribution mechanism. Since CORBA has no built-in support for
-mobile code, new functionality generally has to be installed manually.
-
address@hidden enumerate
-
-Of course a non-agent system can exhibit these same features with some
-work. But the mobile code paradigm supports the transfer of executable
-code to a remote location for asynchronous execution from the start. An
-agent architecture should be considered for systems where the above features
-are primary requirements.
address@hidden quotation
address@hidden ignore
-
When trying to migrate a process from one system to another,
a server process is needed on the receiving side. Depending on the kind
of server process, several ways of implementation come to mind.
@@ -3703,9 +3485,9 @@ function migrate(Destination, MobCode, Label) @{
@c endfile
@end smallexample
-The @code{migrate} function prepares the
+The @code{migrate()} function prepares the
aforementioned strings containing the program code and transmits them to a
-server. A consequence of this modular approach is that the @code{migrate}
+server. A consequence of this modular approach is that the @code{migrate()}
function takes some parameters that aren't needed in this application,
but that will be in future ones. Its mandatory parameter @code{Destination}
holds the
name (or IP address) of the server that the agent wants as a host for its
@@ -3726,16 +3508,16 @@ Each variable in an agent program is local to the
current host and does
@item
The array @code{MOBFUN} shown above is an exception. It is handled
-by the function @code{migrate} and does migrate with the application.
+by the function @code{migrate()} and does migrate with the application.
@item
The other exception is the array @code{MOBVAR}. Each variable that
takes part in migration has to be an element of this array.
address@hidden also takes care of this.
address@hidden()} also takes care of this.
@end itemize
Now it's clear what happens to the @code{Label} parameter of the
-function @code{migrate}. It is copied into @code{MOBVAR["Label"]} and
+function @code{migrate()}. It is copied into @code{MOBVAR["Label"]} and
travels alongside the other data. Since travelling takes place via HTTP,
records must be separated with @code{"\r\n"} in @code{RS} and
@code{ORS} as usual. The code assembly for migration takes place in
@@ -3760,8 +3542,8 @@ The application-independent framework is now almost
complete. What follows
is the @code{END} pattern that is executed when the mobile agent has
finished reading its own code. First, it checks whether it is already
running on a remote host or not. In case initialization has not yet taken
-place, it starts @code{MyInit}. Otherwise (later, on a remote host), it
-starts @code{MyJob}:
+place, it starts @code{MyInit()}. Otherwise (later, on a remote host), it
+starts @code{MyJob()}:
@smallexample
@c file eg/network/mobag.awk
@@ -3776,8 +3558,8 @@ END @{
@end smallexample
All that's left to extend the framework into a complete application
-is to write two application-specific functions: @code{MyInit} and
address@hidden Keep in mind that the former is executed once on the
+is to write two application-specific functions: @code{MyInit()} and
address@hidden()}. Keep in mind that the former is executed once on the
originating host, while the latter is executed after each migration:
@smallexample
@@ -3798,9 +3580,9 @@ As mentioned earlier, this agent takes the name of its
origin
(@code{MyOrigin}) with it. Then, it takes the name of its first
destination and goes there for further work. Notice that this name has
the port number of the web server appended to the name of the server,
-because the function @code{migrate} needs it this way to create
+because the function @code{migrate()} needs it this way to create
the @code{HttpService} variable. Finally, it waits for the result to arrive.
-The @code{MyJob} function runs on the remote host:
+The @code{MyJob()} function runs on the remote host:
@smallexample
@c file eg/network/mobag.awk
@@ -3823,7 +3605,7 @@ function MyJob() @{
@c endfile
@end smallexample
-After migrating, the first thing to do in @code{MyJob} is to delete
+After migrating, the first thing to do in @code{MyJob()} is to delete
the name of the current host from the list of hosts to visit. Now, it
is time to start the real work by appending the host's name to the
result string, and reading line by line who is logged in on this host.
@@ -3923,16 +3705,6 @@ The stock shares to avoid today are these:
@dots{}
@end smallexample
address@hidden
address@hidden Chuck suggests removing this paragraph
-If you are not into stock market prediction but want to earn money
-with a more humane service, you might prefer to send out horoscopes
-to your customers. Or, once every refrigerator in every household on this side
-of the Chinese Wall is connected to the Internet, such a service could
-inspect the contents of your customer's refrigerators each day and
-advise them on nutrition. Big Brother is watching them.
address@hidden ignore
-
The script as a whole is rather long. In order to ease the pain of
studying other people's source code, we have broken the script
up into meaningful parts which are invoked one after the other.
@@ -3952,7 +3724,7 @@ BEGIN @{
@end example
The earlier parts store data into variables and arrays which are
-subsequently used by later parts of the script. The @code{Init} function
+subsequently used by later parts of the script. The @code{Init()} function
first checks if the script is invoked correctly (without any parameters).
If not, it informs the user of the correct usage. What follows are preparations
for the retrieval of the historical quote data. The names of the 30 stock
@@ -4131,7 +3903,7 @@ function Prediction() @{
At this point the hard work has been done: the array @code{predict}
contains the predictions for all the ticker symbols. It is up to the
-function @code{Report} to find some nice words to introduce the
+function @code{Report()} to find some nice words to introduce the
desired information.
@smallexample
@@ -4172,7 +3944,7 @@ function Report() @{
@c endfile
@end smallexample
-The function @code{SendMail} goes through the list of customers and opens
+The function @code{SendMail()} goes through the list of customers and opens
a pipe to the @code{mail} command for each of them. Each one receives an
email message with a proper subject heading and is addressed with his full
name.
@@ -4206,50 +3978,6 @@ Try to find a better one.
Should you find one with a success rate of more than 50%, please tell
us about it! It is only for the sake of curiosity, of course. @code{:-)}
address@hidden
address@hidden chuck says to remove this
-Let us give you one final indication as to what one can expect from
-a prediction of stock data, which is sometimes said to contain much
-randomness. One theory says that all relevant information to be taken
-into account when estimating the price of a stock is contained in the
-stock quotes. Every bit of useful information has influenced the
-fair price. Therefore (the theory says) temporary changes (i.e., fluctuations
-within a minute) have to be purely random. But what is the cause of
-short-term changes in stock prices?
-
-Stock prices are fixed when supply and demand meet each other.
-What people are willing to pay reflects human expectations.
-Human expectations are not necessarily random. On the Internet,
-you can find an elucidating paper about predictability and human
-expectations:
address@hidden://it.ucsd.edu/IT/Newsletter/archives/meir/05meir.html,
address@hidden on ``Universal Prediction of Individual Sequences''}}
-The authors (Feder, Merhav, Gutman) introduce the reader to the subject
-by telling a thrilling anecdote.
address@hidden Shannon, Claude
address@hidden
-In the early 50's, at Bell Laboratories, David Hagelbarger built a
-simple ``mind reading'' machine, whose purpose was to play the ``penny
-matching'' game. In this game, a player chooses head or tail, while a
-``mind reading'' machine tries to predict and match his choice.
-Surprisingly, as Robert Lucky tells in his book ``Silicon Dreams'',
-Hagelbarger's simple, 8-state machine, was able to match the ``pennies''
-of its human opponent 5,218 times over the course of 9,795 plays.
-Random guessing would lead to such a high success rate with a probability
-less than one out of 10 billion! Shannon, who was interested in prediction,
-information, and thinking machines, closely followed Hagelbarger's
-machine, and eventually built his own stripped-down version of the machine,
-having the same states, but one that used a simpler strategy at each state.
-As the legend goes, in a duel between the two machines, Shannon's machine
-won by a slight margin! No one knows if this was due to a superior algorithm
-or just a chance happening associated with the specific sequence at that game.
-In any event, the success of both these machines against ``untrained'' human
-opponents was explained by the fact that the human opponents cannot draw
-completely random
-bits.
address@hidden quotation
address@hidden ignore
-
@node PROTBASE, , STOXPRED, Some Applications and Techniques
@section PROTBASE: Searching Through A Protein Database
@cindex PROTBASE
@@ -4549,8 +4277,8 @@ books on Bioinformatics is
The sequences @emph{gawk} and @emph{gnuawk} are in widespread use in
the genetic material of virtually every earthly living being. Let us
take this as a clear indication that the divine creator has intended
address@hidden to prevail over other scripting languages such as @code{perl},
address@hidden, or @code{python} which are not even proper sequences. (:-)
address@hidden to prevail over other scripting languages such as @command{perl},
address@hidden, or @command{python} which are not even proper sequences. (:-)
@end enumerate
@node Links, GNU Free Documentation License, Some Applications and Techniques,
Top
@@ -5200,7 +4928,7 @@ to permit their use in free software.
@bye
Conventions:
-1. Functions, built-in or otherwise, do NOT have () after them.
+1. Functions, built-in or otherwise, do have () after them.
2. Gawk built-in vars and functions are in @code. Also program vars and
functions.
3. HTTP method names are in @code.
-----------------------------------------------------------------------
Summary of changes:
doc/ChangeLog | 6 +
doc/gawkinet.info | 237 +++++++++++++++++----------------
doc/gawkinet.texi | 390 ++++++++---------------------------------------------
3 files changed, 187 insertions(+), 446 deletions(-)
hooks/post-receive
--
gawk
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gawk-diffs] [SCM] gawk branch, gawk-4.1-stable, updated. gawk-4.1.0-867-g693ca0a,
Arnold Robbins <=