Re: [Arsperl-users] Using ARSPerl to Build a Web Interface

[Mike W. <mdw...@gm...>]

Forgive me for being dense, but I don't understand how one would tie a
control record that was created from a login routine, for example, to a
session ID or similar. Given a session ID, how does one tie that to a
control record that has already been created/validated?

In other words, where does the control record "live" and how does one get at
it? Doesn't the control record "disappear" once the web server request is
complete?

Mike

On 6/26/07, Axton W Grams/NYLIC <Axt...@ne...> wrote:
>
>
> I assume you will be writing the interface as a perl CGI.
>
> Question 1: Using a Session Cookie is one way
> http://www.webmasterworld.com/forum13/4021.htm
> http://jan.newmarch.name/ecommerce/session.html
> http://www.perlmonks.org/?node_id=2746
>
> Question 2: mod_perl is an apache thing.  writing your apps as a cgi
> script will ensure that people on any web server capable of cgi can run the
> scripts.  I run the arswiki.org bugzilla app using mod_perl, but it was
> originally run as a cgi.  mod_perl does require much more memory than a
> regular cgi, but on the flip-side, it is also much faster.
>
>
> Axton Grams
>
>
>
>
>  *"Mike Wallick" <mdw...@gm...>*
> Sent by: ars...@ar...
>
> 06/26/2007 12:15 PM  Please respond to
> ARSperl User Discussion <ars...@ar...>
>
>   To
> ars...@ar...  cc
>
>  Subject
> [Arsperl-users] Using ARSPerl to Build a Web Interface
>
>
>
>
>
>
> 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
> Ars...@ar...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>
>
> -------------------------------------------------------------------------
> 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
> Ars...@ar...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>
>