comment on

I post my troubles with great hesitation... Again, I've looked all over for information about logins with CGI::Application and CGI::Application::Session. I've super searched, I've Googled, and I've wiki-ed. None of it seems to make enough sense for me to keep coding.

All I've gathered so far is that many would prefer to seperate authentication and the actual guts of the program into two C::As. But I don't get it? Why? Why do that?

Questions like... Which parts of the program actually need to be run modes? The nouns (results) or the verbs (the actions)? Where does my validation function go? How do I store/work with a session? How do I debug C::A?

I don't know. I'm so confused. I wish someone would just hold my hand and post a very concrete example of a C::A with login. I've read through so many already (its been hours) and none of them make sense. Again, I feel silly.

Thoughts, oh wise ones?

Edit: Forgot to mention the use of C::A::S...

In reply to Starting with CGI::Application(::Session) and Logins by deep submerge

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.


No such thing as a small change
	PerlMonks