Paketname | libclass-dbi-fromcgi-perl |
Beschreibung | Perl module to update Class::DBI data using CGI::Untaint |
Archiv/Repository | Offizielles Debian Archiv squeeze (main) |
Version | 1.00-4 |
Sektion | perl |
Priorität | optional |
Installierte Größe | 72 Byte |
Hängt ab von | perl (>= 5.6.0-16), libclass-dbi-perl (>= 0.93), libcgi-untaint-perl (>= 0.8) |
Empfohlene Pakete | |
Paketbetreuer | Debian Perl Group |
Quelle | |
Paketgröße | 12006 Byte |
Prüfsumme MD5 | 7b6b2b038203166ffb41408b4144db6f |
Prüfsumme SHA1 | 98f0d576614e2ec15550b60c407804f182f4fa92 |
Prüfsumme SHA256 | 5681ca947e81d9d903d18b3aa95ace0a256626c7383f79b39489b56ac463b871 |
Link zum Herunterladen | libclass-dbi-fromcgi-perl_1.00-4_all.deb |
Ausführliche Beschreibung | Lots of times, Class::DBI is used in web-based applications. (In
fact, coupled with a templating system that allows you to pass
objects, such as Template::Toolkit, Class::DBI is very much your
friend for these.)
.
One of the most irritating things about writing web-based applications
is the monotony of writing much of the same stuff over and over again.
And, where there's monotony there's a tendency to skip over stuff that
is really important, but is a pain to write - like Taint Checking and
sensible input validation. (Especially as you can still show a 'working'
application without it!). CGI::Untaint can take care of a lot of that
for us.
.
It so happens that CGI::Untaint also plays well with Class::DBI. All
you need to do is to 'use Class::DBI::FromCGI' in your class (or in
your local Class::DBI subclass that all your other classes inherit
from. You do that, don't you?).
|