Hey all. So I'm working on a proof of concept idea for myself. I want to look into rolling my own web interface to Remedy using ARSPerl, and before I go too far down that road, I wanted to ask everyone to share any and all experiences (if any) they may have had. I'm fairly familiar with Perl development for tools and the like, but I'm new to using Perl for web interfaces (but not web interfaces in general).
Specifically: 1.) How would one go about keeping a user's session in tact? I'd like to have a control record for each individual user, rather than write code to always log in to the server with a static username/password, and then "proxy" that superuser to a "real" user. Is this even possible/a good idea? Would it be possible to implement this at the Apache server level using mod_perl or something similar? 2.) (a bit OT): Since I'm new to Perl web development, are there any sort of best practices or guidelines for Perl web development? Should I be using mod_perl, CGI, roll my own, etc.? I've been scanning the mod_perl docs, and that looks promising, but before I get too deep, I wanted to see if anyone had an opinion about whether this is even worth the time or not. Thanks everyone. Mike ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Arsperl-users mailing list Arsperl-users@arsperl.org https://lists.sourceforge.net/lists/listinfo/arsperl-users
