In an ideal world all
session mgmt and user authentication would be application level with high granularity - down to each page or function call
from the client, every time a request arrives. I know of no current solution, Perl or otherwise, that solves this completely.
Would love to see one though.
Yes, this level of authentication can certainly be done.
I'm currently involved in a large project, where this is
being done, and we even go further. Unfortunally, I can't
tell you more.
It's not simple, and it takes large investments.
The question isn't "can this level of authentication be done",
the question is "how much are you willing to pay?" (pay in a
broad sense - mostly costs to hire people).
Abigail
-
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.
|
