Re: [cgiapp] Re: multiple run modes in template and form validation

2005-12-15 Thread Michael Gwin
- I assume you are using ValidateRM. There's an option to pass arguments to HTML::FillINForm. Sounds like you need 'ignore_fields' there. More details in the FiF docs. Thanks, Mark. Works perfectly - I should have found this myself. Mike

Re: [cgiapp] Re: C::A::Dispatch changes

2005-12-15 Thread Michael Peters
Mark Stosberg wrote: Michael, First, thanks for picking up the torch of implementation on this. No problem. I'm just trying to finalize the API and haven't actually started the implementation yet, so you might want to wait to thank me :) :app - will be converted into the module name using

Re: [cgiapp] C::A::Dispatch changes

2005-12-15 Thread Michael Peters
Michael Graham wrote: This looks great! I like the lower case params. that seems to be the general consensus, so that's probably the way it'll go. I'm also thinking about adding the rule that module-name would become ModuleName I like this a lot, too. I think it covers the last

Re: [cgiapp] Working with proxies.

2005-12-15 Thread Webmaster Techcode.NET
Hello. I already have those pragmas inside templates - as meta tags. So it's not browsers fault. But I doubpt that proxy parses html - adding that to header should do the trick as this Free Proxy claims that it folows some RFC regulation related to caching/proxying. Thanks. - Original

[cgiapp] Re: C::A::Dispatch changes

2005-12-15 Thread Mark Stosberg
On 2005-12-15, Michael Peters [EMAIL PROTECTED] wrote: As long as no one has underscores in their module names, we're safe. That could be worked around if it comes up. That's a pretty rare case, but right now, the user can just override get_module_name(). I don't plan on taking this method

Re: [cgiapp] Working with proxies.

2005-12-15 Thread Rob Kinyon
I do the following: use POSIX qw( strftime ); $self-header_add( # date in the past -expires = 'Sat, 26 Jul 1997 05:00:00 GMT', # always modified -Last_Modified = strftime('%a, %d %b %Y %H:%M:%S GMT', gmtime), # HTTP/1.0 -Pragma

[cgiapp] C::A::P::Session

2005-12-15 Thread bradford
Just started working with CGI::Application::Plugin::Session and am confused about a few things: 1) I'm used to CGI::Session, where I have to assign a cookie name and the deal with a session id generated by C::S and written into the cookie. How is the session id and cookie name handled in