I'm still stumbling along in trying to get this going. But, maybe
some of this is of interest. Or maybe people can clear things
up.
It's a CGI version I am setting up, but for now I am using
maypole_test.pl to work with using perldb in emacs. SQLite is
the database backend.
When looking at the mailing list archives, I seen a few posts
about performance. So, my first thing is an observation on that.
I have half a dozen tables inside a database, most of the tables
only have 3 or 4 columns.
To get to the point in my module (ElugRev.pm) where I call
->setup("dbi:...") is about 28k single steps. Which is a lot of
setup. All of the tables are in a single database, but for every
table the system initializes itself which the expected dialect of
SQL being used (same for all of them, so shouldn't that only be
done once?). Then it reads the CREATE statement for the various
tables from the database, and analyses that SQL statement for
being valid. While this is good in the case of SQL statements
provided by a user, is this really necessary for the SQL
statement which successfully made the table in the database you
are connecting to?
The current debug session of Maypole is going to die sooner or
later as well, because in the handler() function of Maypole.pm, a
call to $r->get_request( $req ) is made. It isn't really CGI
inside emacs, and I am not using the CLI version of Maypole
either. So, a
400 Unknown method No REQUEST_METHOD received
was generated (before headers printed). But, I'll see if anything
else gets tripped up on this pass through emacs. :-)
>From some readings in the PHP world talking about cookies and
session variables, I am expecting that something to do with
cookies needs to get called early on with Maypole as well. Is
this the case, or does something else happen?
Thanks,
Gord
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT