There are several points to note from this example:
- The request is made up of three distinct parts: one part (in this case
the phone number DOTCOM plus "example") designates the location of the CMRL
document, one part (in this case "something") designates the "path" that is
compared against the match patterns specified in the CMRL document, and one
part (in this case "red") designates the "argument" that is passed to the
engine.
- There is no explicit delimiter between the path and the argument. The
system must route the request (by comparing the request against the match
patterns specified in the CMRL document) in order to determine which portion
of the request is the path and which part of the request is the argument.
- The system posts the argument to the engine as the parameter
"sys_argument." The system also posts other parameters to the engine (as
described below).
- The engine returns a CMRL <message> tag, which is the simplest
example of a CMRL "terminating node."
In a nutshell, this is how DOTGO engines work: the system extracts the
argument from the request by comparing the request against the match patterns
specified in the CMRL document, the system posts the argument (and other
parameters) to the engine, and the engine returns a CMRL terminating node.
