Re: [Openaaq-discuss] How to make AAQ running on windows

[Alex P. <ale...@zw...>]

Michael, I have a bunch of questions for you.

What version of MySQL are you running?

Are you using a standard perl module for te HTML templates?

You wrote two scripts, but OAAQ has the database driven functions for
creating modified pages for just such an implementation. Did the
shared.pl code (gross as it is) get in your way?

I like your Net::SMTP implementation. That would take one more
uncertainty out of installation. I may grab that idea.

I'm pushing myself to redo post.pl under the followig design:

1. same one page model; any preceeding pages can be used to profile a
user by imagemap, preceeding form or a user login mechanism belonging
to the site.

2. Complete HTML page or Apache server side include. a server side
include is called in the page with
<!--#exec cmd="/location/post.pl '$QUERY_STRING'" -->
and this permits OAAQ to function in complicated HTML sites. Also, you
will one day be able to use c/post.pl to add a post form to the same
page that c/search.pl adds a search form to.

3. OAAQ in server side includes mode will return a redirect to a success
page.

4. Email verification will split email on the @ and attempt to resolve
the IP address of the mail server. I'm guessing Net::SMTP could request
verification of an account from a mail server, but I think too many
servers will not reply out of some setting meant to filter spam.

5. support for sites reuiring no email in favor of phone. Later, I will
look at staff modules to allow phone as the responce method and a "do
not send responce" swich.

6. create a new client record for every post. that may seem like bad
database design, completely ignoring normalization, but without a
verifiably unique key I'm stuck.

Alex









ope...@li... wrote:
> 
> 
> Hello Everyone,
> 
> I also have something to contribute. Recently I re-wrote the AAQ client
> (post.pl essentially). I wrote two new version (one for the public
> library users at my consortium and one for the post-secondary users). I
> made some significant changes.
> 
> 1) The HTML the program displays and the email it sends out are based on
> templates
> 2) I use Net::SMTP to send email
> 3) There is more error checking in the database code
> 4) I use transactions in the database code (so if one pieces fails the
> whole thing stops and rollsback what it was doing).
> 5) User registration is not required (the system stores all the user
> info but does not track the user's identity with a cookie)
> 6) One screen is used to collect all information from the user
> 
> I will make the new code available as soon as possible.
>