Yes, when working on code in spurts it's always harder to get back into it. My job is half perl, half general system administration, and not split in even halves. :) It's both all day, interrupting programming time with floor calls and hardware problems all day long. It can make remembering where you were a chore...
Just a side note....You realize of course that just putting a username in a cookie is not at all secure. Anyone can fake a cookie with ease. So it's probably fine for a protected intranet app with trusted users, but if you're trying to keep unauthorized folks out of a public website, that's not going to do it. Your best bet if you need more options than .htaccess files is to look into the Apache::AuthCookie module. I use a subclass of it called Apache::AuthCookieDBI, and though it wasn't all that easy to get going, I love it now.
cheers!
-
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.
|