CGI::Session or a database are the conventional ways of storing information pertaining to a session or a user. Using a cookie (which CGI::Session manages for you) or some get data embodied in the URL is generally the way you track a session.
The trick is to use a key (in the URL) that provides access to the server side stored information for the session. Often an MD5 hash of something like a user ID and login time is used to provide the key.
DWIM is Perl's answer to Gödel
| [reply] |
The only ways to get information to your script from a client are cookies, forms, and the URL. You can use cookies to create sessions, where you store the information on the Web server and just pass enough information to find the session data. You can use forms with hidden elements to pass information to your script that is not entered by the user. Forms which use the GET method will have the parameters show up in the URL; with the POST method the parameters will not be visible in the URL.
From your example, it looks like the user may be entering private information you don't want to show up in the URL. In that case, a good solution is to have the user enter the information into a form which uses the POST method, and make sure the server is using SSL so the data is encrypted, and so the browser is more careful with the information in its history.
Hopefully that will be enough to get you started.
| [reply]
[d/l]
[select] |
Can you please explain the method in which user enters the information into a form...thanks !!
| [reply] |
Data from the form can come from user input from the various HTML input elements (textboxes, buttons, dropdowns, radio buttons, etc), or from data embedded in the HTML document by the server using hidden form elements, like this:
<form>
<input type="hidden" name="var1" value="val1">
<input type="hidden" name="var2" value="val2">
<!-- ... -->
</form>
| [reply]
[d/l] |
if u want to transport data to several pages u can use input hidden fields, so u don't need to mess up ure url or store everything in cookies
kd ultibuzz
| [reply] |
