Hi all, my next job now that I should finally have some time available is to rework handler and handler_guts methods so that HTTP status codes are used rather than the internal maypole ones.
The benefits of this would be that http redirects and custom 500/404 pages would work within maypole correctly. I see that as pretty essential, so I want to get it fixed ASAP. Once I've done that (which should be early in the week), I'm going to try and get a simple version of a new maypole site done - using the custom hacked mitiki I have on my laptop. Finally once those are done, the last essential element of the 2.11 release will need to be finished - form handling. I'm going to have to reign in my ambitions with this I think and subclass the existing CGI/DBI::Untaint instead of replacing them, while applying some improvements to the Model. This should be enough to make form handling more acceptable out of the box, but I believe that for the long term Untaint leaves too much to be desired. regards, Aaron ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
