Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Authentication in web applications

by kirbyk (Friar)
on Jun 07, 2005 at 23:44 UTC ( #464497=note: print w/ replies, xml ) Need Help??


in reply to Authentication in web applications

One thing that may or may not be a factor - multiple web servers. Once you make that architectural leap, apache-based models start failing you, as do a lot of session methods, and you're left with cookies (or a universally passed session ID param) on the user side, and database on the backend with info about sessions.

Which isn't to say that there's not a better way, but this is a big factor to consider for any reasonably large web site. Which most sites aren't, so, there you go.

-- Kirby, WhitePages.com


Comment on Re: Authentication in web applications
Re^2: Authentication in web applications
by perrin (Chancellor) on Jun 08, 2005 at 02:01 UTC
    Using Apache:: modules doesn't imply any specific storage mechanism. It's about how you tie into the server's request pipeline, not about what you do once you're there.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://464497]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2014-07-25 05:09 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (167 votes), past polls