On Fri, Jan 15, 2010 at 9:38 PM, lanas <la...@securenet.net> wrote: > Le Vendredi, 15 Janvier 2010 09:43:36 -0500, > Alejandro Imass <aim...@corcaribe.com> a écrit : > > Thanks for the comment. My motivation to go with something that looks > like a framework to produce web-based interfaces is based on perception > of ease of getting it going. So that the main work would remain with > making the actual application better, not on the web interface. > > Since you suggest using CGI:Application and a POE HTTP server (which > one could be good for that ?) I'll then take a look and try to evaluate > the overhead. I'm somewhat familiar with the TT, so that's mostly OK. >
CGI::Application is just a design pattern over CGI which by itself is very powerful also. For an administratrive interface which does not need to be pretty but rather functional, you could probably even skip a templating tool altogether, IMHO, just build your HTML app directly from perl using the CGI HTML objects and methods. > Having a POE HTTP server would certainly make the integration with the > application easier, which is a plus. Is there a SSL option with any of > the POE HTTP servers ? > POE::Component::Server::SimpleHTTP seems to support ssl although I could not say for sure since I haven't tested that personally. Anyway, you mentioned that it was an admin app in an intranet, why use ssl instead of just blocking access by IP or just use simple HTTP authentication. SSL is really not that effective in an LAN because of the relative easeness of arp poisoning and the stupid users will almost allways (99.9% in my personal experience) click OK to a forged certificate by something as simple to use as ettercap, for example. Cheers -- Alejandro Imass
