[Maypole] User Validation (eventually)

[Gordon Haverland]

I'm still stumbling along in trying to get this going.  But, maybe=20
some of this is of interest.  Or maybe people can clear things=20
up.

It's a CGI version I am setting up, but for now I am using=20
maypole_test.pl to work with using perldb in emacs.  SQLite is=20
the database backend.

When looking at the mailing list archives, I seen a few posts=20
about performance.  So, my first thing is an observation on that.=20

I have half a dozen tables inside a database, most of the tables=20
only have 3 or 4 columns.

To get to the point in my module (ElugRev.pm) where I call=20
=2D>setup("dbi:...") is about 28k single steps.  Which is a lot of=20
setup.  All of the tables are in a single database, but for every=20
table the system initializes itself which the expected dialect of=20
SQL being used (same for all of them, so shouldn't that only be=20
done once?).  Then it reads the CREATE statement for the various=20
tables from the database, and analyses that SQL statement for=20
being valid.  While this is good in the case of SQL statements=20
provided by a user, is this really necessary for the SQL=20
statement which successfully made the table in the database you=20
are connecting to?

The current debug session of Maypole is going to die sooner or=20
later as well, because in the handler() function of Maypole.pm, a=20
call to $r->get_request( $req ) is made.  It isn't really CGI=20
inside emacs, and I am not using the CLI version of Maypole=20
either.  So, a
 400 Unknown method No REQUEST_METHOD received
was generated (before headers printed).  But, I'll see if anything=20
else gets tripped up on this pass through emacs.  :-)

=46rom some readings in the PHP world talking about cookies and=20
session variables, I am expecting that something to do with=20
cookies needs to get called early on with Maypole as well.  Is=20
this the case, or does something else happen?

Thanks,
Gord