From Seo Wiki - Search Engine Optimization and Programming Languages
A webform on a web page allows a user to enter data that is sent to a server for processing. Webforms resemble paper forms because internet users fill out the forms using checkboxes, radio buttons, or text fields. For example, webforms can be used to enter shipping or credit card data to order a product or can be used to retrieve data (e.g., searching on a search engine).
In addition to functioning as input templates for new information, webforms can also be used to query and display existing data in a similar manner to mail merge forms, with the same advantages. The decoupling of message structure and underlying data allow both to vary independently. The use of webforms for this purpose avoids the problems associated with explicitly creating separate web pages for each record in a database.
Webforms are defined in formal programming languages such as HTML, Perl, Php, Java or .NET. The implementations of these languages often automatically invoke user interface idioms, such as grids and themes, minimizing programming time, costs and risks.
The following elements can make up the user-inputting portion of a form:
- input field
- text – a simple text box that allows input of a single line of text
- checkbox – a check box
- radio – a radio button
- file – a file select control for uploading a file
- reset – a reset button that, when activated, tells the browser to restore the values to their initial values.
- submit – a button that tells the browser to take action on the form (typically to send it to a server)
- textarea – much like the text input field except a textarea allows for multiple rows of data to be shown and entered
- select – a drop-down list that displays a list of items a user can select from
The sample image on the right shows all of these elements:
- a text box asking for your name
- a pair of radio buttons asking you to pick your sex
- a select box giving you a list of eye colors to choose from
- a pair of check boxes to click on if they apply to you
- a text area to describe your athletic ability
- a submit button to send it to the server
XForms is an alternative standard that was designed to represent the next generation of HTML / XHTML forms. It is also a standard that is generic enough to be used in a standalone manner or with presentation languages other than HTML or XHTML to describe forms in other user interfaces. Unlike HTML / XHTML forms, XForms uses a Model-View-Controller approach.
An XForms document can be as simple as an HTML / XHTML web form. But XForms includes many advanced features. For example, the form can react in real time and request and retrieve new information while it is still being displayed, without the use of a separate scripting language. The form can specify how its data should be validated or how portions of the form may change depending on data entered in other parts of the form.
Unlike HTML / XHTML forms, XForms is not yet supported on currently available web browsers.
Combined with programs
While client-side languages used in conjunction with forms are limited, they often can serve to do pre-validation of the form data and/or to prepare the form data to send to a server-side program.
Server-side programs can do a vast assortment of tasks to create dynamic web sites — from authenticating a login through, for example, Lightweight Directory Access Protocol to retrieving and storing data in a database to spell checking to sending e-mail — quite unlike client-side programs. Most server-side program requests must pass through the web server's Common Gateway Interface to execute the program to actually perform the tasks.
Scripting languages are the most common server-side programs used for web sites, but it is also possible to run compiled programs.
Some of the scripting languages commonly used:
Some of the compiling languages commonly used:
PHP is one very common language used for server-side languages and is one of the few languages created specifically for server-side programs.
A PHP script may:
- display the information on another page (ex: asking for a user's name and then displaying it on the web page)
- act as a logon interface
- post the data to a database (ex: mySQL, an ASCII file, etc.)
- store the information on the viewer's computer in an HTTP cookie
- generate an e-mail, either using the data or including said data in the e-mail's contents (possibly as an e-mail attachment)
The HTML form learns where to pass the data from the action attribute of the form's HTML element. The target PHP file then retrieves the data either through POST or GET (see HTTP for more information), depending on the programmer's preference. Here is a basic form handler PHP script that will post the form's contents, in this case "user", to the page using GET:
<html> <body> <form action="form_handler.php" method="get"> User Name: <input name="user" type="text" /> <input type="submit" /> </form> </body> </html>
<html> <body> <?php /* * This will print whatever the user put into the form on the form.html page. */ $name = $_GET['user']; echo "Hello, ". $name ."!"; ?> </body> </html>
In the above script the $_GET[''] and $_POST[''] commands need to be changed, depending on what is used in the form, however $_REQUEST[''] is used for both so it is more efficient to use for form collection.
Perl is another language often used for web development. Perl scripts are traditionally used as Common Gateway Interface applications (CGIs). In fact, Perl is such a common way to write CGIs that the two are often confused. CGIs may be written in other languages than Perl (compatibility with multiple languages is a design goal of the CGI protocol) and there are other ways to make Perl scripts interoperate with a web server than using CGI (such as FastCGI or Apache's mod perl).
Perl CGIs were once a very common way to write web applications. But not being specifically designed for web development, Perl is now often viewed as less practical (both for developers and users) than specialized languages like PHP or ASP. This is especially true if Perl modules would need to be installed on the web host or if wanting to use a non-CGI environment that might require extra configurations on the web server. Some web hosts also rely on interpreter-level sandboxing, which while possible with the Safe module, wouldn't be very practical and undoubtly break a lot of scripts considering common practices. Similar considerations might apply to other general-purpose scripting languages like Python or Ruby. For these reasons, a lot of cheap web hosts nowadays effectively only support PHP and web developers often seek compatibility with them.
A modern Perl 5 CGI using the standard CGI module with a form similar to the one above might look like:
#!/usr/bin/perl use CGI qw(:standard); $user = param('user'); print header; print html( body( p("Hello, $user!"), ), );
Among the simplest and most commonly needed types of server-side script is that which simply emails the contents of a submitted form. This kind of script is frequently exploited by spammers, however, and many of the most popular form-to-email scripts in use are vulnerable to be hijacked for spamming purposes. One of the most popular scripts of this type was "FormMail.pl" made by Matt's Script Archive. Today, no version of this still frequently used script is considered secure.
To avoid the confusion and difficulty of installing and using scripts, webmasters often use a free forms processing service to get their forms working.
- Forms in HTML documents, the W3C's spec page for forms in HTML 4.
- Wikibooks: HyperText Markup Language/Formsde:Webformular