Another way to handle the logging in and out is by setting a cookie:
- When the user logs in, use CGI to write a cookie containing their user name, possibly a code for their priviledges, and then an expire time.
- Each time you return to a server-side script, check the cookie. If it has expired, route them to the log in screen. If it has not expired, reset it and send them on their way.
- When they voluntarily log out, set the cookie's expire time to zero and return them to the log-in screen.
It boils down to what you are most comfortable with, though the DB method has the advantage of allowing you to know who is logged on at any one time.
—Brad
"Don't ever take a fence down until you know the reason it was put up." G. K. Chesterton
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
