in reply to Book Reccomendation for Web Development using Perl

HI, I know there are a lot of good perl books out there. I just realised my programming skills are not that great..as ive been using google to do most of my perl code.

You skills aren't too far from removed from great, and your attitude is great :)

See these links here Re: Perl and Fastcgi + template system (confused) like Web Programming: For Beginners and to learn about the internet

and Watch the videos on perlmaven linked here http://szabgab.com/catalys-dancer-mojolicious.html

The documentation for gr8 modules like CGI::Application and CGI::Session does not delve into the depths of how the session variables are managed, so its difficult to get an understanding of the underlying session management. Thats where my actual problem starts, and i'm having to use logging statements everywhere to figure out stuff..

Do you understand cookies? Did you read CGI::Session::Tutorial

See code and my links at Problems with session expiration

Then forget about "use CGI::Session;" because that is low level stuff (like "use CGI", see Re: ModPerl Registry vs Apache Handlers (neither))), you want to use Dancer/Mojolicious... this is higher level easy way ... don't skip reading the other tutorials if you need refresher about HTTP/CGI, but to start writing code stick with mojo or dancer

  • Comment on Re: Book Reccomendation for Web Development using Perl

Replies are listed 'Best First'.
Re^2: Book Reccomendation for Web Development using Perl
by Anonymous Monk on Oct 13, 2014 at 10:16 UTC
    A good regular perl book is chromatics free book Modern Perl a loose description of how experienced and effective Perl 5 programmers work....You can learn this too.
Re^2: Book Reccomendation for Web Development using Perl
by perlron (Pilgrim) on Oct 14, 2014 at 07:02 UTC
    Ok. hats off. you're giving me so much good "gyan" a term we use in India ..i cant take it:D im not a big fan of cookies in web development, and i want to use only CGISESSID (which i now know also shows up as a cookie). Will check out problems with session expiration too.
      i feel dancer and mojo simplify things to the point you dont need to know the basics any more. just call the get and post urls and your app is up. like its only because of legacy modules like CGI::Application i understood the value of Template Toolkit, though even dancer uses TT. But yes, dancer is so classy and light. i will use it sooner than..
        i feel dancer and mojo simplify things to the point you dont need to know the basics any more.
        Yes and no at same time.
        They are frameworks written in Perl to produce web applications written in Perl: they aim to hide you dirty work and they aim to do the right think unseen. Are easier to use? comparing to old CGI's? This is up to you. For sure are easier to use if you wont do the right thing with a secure, stable, deployable, maintenable, inspectable.. web application.

        While Dancer2 (yes now is Dancer2 please search for it) is simpler then Mojo there is always a lot to learn.

        The central point is: Mojo and Dancer2 and other modern tools let you to use PSGI. That protocol, specification, is the ribirth of Perl in web context: CGI was good in the past, but, sad to inform you, is dead.

        Search around for PSGI (the specification) and Plack (the implementation) you'll realize it too. While you can write a web application entirely by your own in the rails of PSGI, is more sane to use a framework that make your life easier.

        HtH
        L*
        There are no rules, there are no thumbs..
        Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.