In later lessons it might mean passing it to an email program or adding it to a database or replacing it with some random text to really freak out the user. If you've been thinking about how your form is laid out you might be thinking that you can save some serious processing time by just remembering what order your fields are in and assigning the data to variables based on that. Thus, the data in item 1 is from field 1 so it goes in variable 1, and so on. WWW clients are not required to return the form data in the order that the fields occur in the form. If they want to do so, they can reverse the fields or even randomly mix them up before returning them.
Rigid protocols leave little room for later improvements.
HTTP is so loose that there's tons of room for improvement. That's the Submit button. You could use Tokenize to do this as well if you wanted. I'm not sure how much it would improve the speed, though, and I'm not very interested right now in finding out. I'm ignoring a big factor - whether the data is actually correct.