Thanks, Rereading the paragraph yet again, I see that you are right, but it still seems a bit ambiguous:
(quoted from http://www.masonbook.com/book/chapter-8.mhtml) ()This is a component from which the top-level autohandler, /autohandler, inherits. Its job is to ()create a few objects that are used on almost every page. While some components don't inherit from ()the autohandler, they still inherit from this component in order to be able to use these objects. So they create the syshandler file and flag an inherit in autohandler, which is auto-inherited unless otherwise specified. Then when you don't need the formatting in autohandler for a component, you can specify syshandler to replace autohandler. Cool. thanks, JimB > ----- Original Message ----- > From: "Malcolm J Harwood" <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: [Mason] syshandler > Date: Tue, 14 Mar 2006 09:34:36 -0500 > > > On Tuesday 14 March 2006 09:17 am, Jim Babcock wrote: > > > I'm trying to follow the Mason books apprentice.perl.org example for login > > and session management and I'm having and issue with 'syshandler'. > > > > The book alleges that a file called 'syshandler' will get called first, > > even before autohandler and even when autohandler is not called. It says > > that syshandler is the ideal place for setting up database handles and > > session cookies and such. > > > > I've tried mimicking what the book does and it doesn't seem to recognize > > it. Digging into the example from the book, it seems to hook it into the > > autohandler with an inherit. > > > Is the syshandler something they made up or is it a real component of > > mason? > > It isn't part of mason's inherit chain. It's a suggestion of one way of > implementing things. Thus the need to explicitly inherit it in your base > autohandler. > > You can put all your db connectivity code in your base autohandler if you > wish. The advantage of using a separate component is that you can make your > autohandlers just about display, localise your session management in one > place and wrap the "call_next" in an eval so you can do something useful if > your autohandler throws an error. > > Alternatively you just write a perl module that wraps your session management > for you and initialise that from your autohandler. > > > Also, it seems like mason doesn't tell you when things fail, it tells you > > when you try to use them next time and that fails... is that a fair > > characterzation? > > Not in my experience, usually it yells at me right away. > > > -- > "...I was feared and worshipped across the mortal globe. And now I'm > stuck at Sunnydale High. Mortal. A child. And I'm flunking math." > - Anya, Buffy the Vampire Slayer: Doppelgangland > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Mason-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mason-users > -- ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
