NetAlive Documentation

HTTP Access Widget

Input 9: POST data (see below).
Inputs 8-11: data inputs see below.
Input 7: contributes to URL (see below).
Outputs 2-4: data outputs (all the same).

Receives a URL (POST data, extra headers, ...) as input, accesses the URL over the Internet, and sends the result to output. Many variants for different protocols.

Behavior

Access a URL (not necessarily via HTTP) and transmits the received data on all outputs.

The URL is formed from the widget's address field ("Computer to run on") and 7 o'clock address input. If the address is empty, the 7 o'clock address input becomes the URL. If the address is not empty it gets used as a pattern: data on the 7 o'clock input replaces "$" characters in the address field. (Example, address: "http://url?parameter=$," 7 o'clock input: "testing," actual URL: "http://url?parameter=testing.")

The 9 o'clock input conveys POST data. If a 9 o'clock input is present, the method becomes POST and POST data is formed from the widget's "Internal data" field and 9 o'clock input. If the internal data field is empty, the 9 o'clock input becomes the POST data. If the internal data field is not empty, it gets used as a pattern: data on the 9 o'clock input replaces "$" characters in the internal data field. (Example, internal data: "name=$," 9 o'clock input: "NetAlive," actual URL: "name=NetAlive.")

The 10 o'clock input conveys extra headers. If a 10 o'clock input is present, the method becomes POST (possible misdesign: should it leave method alone?) and the data on the 10 o'clock input is used as additional metadata in the URL's access.

If the 9 and 10 o'clock inputs are not connected, GET is used as the access method.

The description above is clear if the URL's scheme is "http." Otherwise, the POST data, the method, and the extra headers are given an interpretation appropriate to the scheme.

Note: there may be an arbitrary number of outstanding requests at any time.

Note: this is a RPC-type task. Normally, the address specifies a computer on which NetAlive enables the task. In an RPC-type task, NetAlive on the application's console initiates a Remote Procedure Call (RPC) to the addressed host. NetAlive does not need to be present on the addressed host.

Variants

HTTPForm causes the access to be a form submission. Data from the 9 o'clock input becomes the form's data.

Appearance

Invisible.

Interactive Demonstration

Press to invoke http.net.

The pushbutton "Initiate Access" sends a NULL message to a HTTP Access task. The task has the NetAlive home page URL (http://www.netalive.com) built into it. Upon receiving the NULL message, the task accesses the URL and sends the result to the Textual HTML "Result" widget.

Type a host name into the field "Type a URL without leading "http://"" (i. e. type "www.netalive.com" for "http://www.netalive.com"). The text replaces "$" in the pattern "http://$" in an HTTP Access task. Net Alive! accesses the resulting URL and puts it into the Textual HTML "Result" widget.

Type some words into the field "Enter some misspelled words." The text becomes form data for an HTTP Access task. The URL specifies a spelling check program at the NetAlive web site. The data returned is a brief report of misspelled words in the submission.


[NetAlive Documentation Home Page][NetAlive Home Page]