[cgiapp] Re: header_props after header_type (was: cgi_minimal compatible?)

2003-11-02 Thread Mark Stosberg
On 2003-11-02, Mark Fuller [EMAIL PROTECTED] wrote: I've been using cgi::application (and html::template) for the last few days. Wow, this is the cloest thing to perfection I've seen. I believe the documentation should note that header_props should be set only *after* header_type. I was

Re: [cgiapp] Re: header_props after header_type (was: cgi_minimal compatible?)

2003-11-02 Thread Mark Fuller
From: Mark Stosberg [EMAIL PROTECTED] I believe your finding is incorrect. I think you are correct. Now I believe that I overlayed my header_props by setting one property (a cookie) and then setting it again with the redirection URL. (I thought that setting the header-type to redirect did it.

[cgiapp] Re: header_props after header_type (was: cgi_minimal compatible?)

2003-11-02 Thread Mark Stosberg
On 2003-11-02, Mark Fuller [EMAIL PROTECTED] wrote: I think you are correct. Now I believe that I overlayed my header_props by setting one property (a cookie) and then setting it again with the redirection URL. (I thought that setting the header-type to redirect did it. But, it looks like it

[cgiapp] CGI Error handling

2003-11-02 Thread Mark Fuller
What's a good way to abort normal processing and display a simple error message? For example, let's say I insert a row into a MySQL table and it fails. I don't want to develop a lot of processing (beyond perhaps sleeping 5 seconds and trying again) to accomodate this. I just want to display a

[cgiapp] teardown method

2003-11-02 Thread Mark Fuller
For session tracking, I keep the values in a hash and update the table in the teardown method. I thought this would be a faster way to update the session-tracking table because, by then, I the runmode would have emitted its output and the visitor would be receiving the page while the teardown