Re: [Catalyst] How to do REST without deserializing uploaded files (PUT)

On Tue, Mar 31, 2009 at 09:03:15PM -0700, Bruce McKenzie wrote: > Is there a way to declare some paths as NOT subject to deserialization? The > reason I ask is that I want it for most everything...just not for a few paths. Instead of deserializing in begin() (as C::C::REST does for you), this migh

[Catalyst] How to do REST without deserializing uploaded files (PUT)

I have a controller subclassed from Catalyst::Controller::REST. Most of my methods are happily ActionClass('REST')'d, but I have one where I want a file to be uploaded and NOT deserialized. Even if I did not include the ActionClass attribute, I would get a complaint about no deserialization m

Re: [Catalyst] How to detect if the current form request is a post?

Thank you:) Yep, and I am aware of GET as a form request method and yes, i hate it. haha K. akimoto Quoting "J. Shirley" : > On Tue, Mar 31, 2009 at 4:01 PM, wrote: > > > > > hi all > > > > In Ruby we can detect if the current form's request is a post or > not. > > > > def controller_action

Re: [Catalyst] How to detect if the current form request is a post?

On 01/04/2009, at 10:47 AM, J. Shirley wrote: On Tue, Mar 31, 2009 at 4:01 PM, wrote: hi all In Ruby we can detect if the current form's request is a post or not. def controller_action if request.post? # Process post data as the user has submitted the form. else # D

Re: [Catalyst] How to detect if the current form request is a post?

On Tue, Mar 31, 2009 at 4:01 PM, wrote: > > hi all > > In Ruby we can detect if the current form's request is a post or not. > > def controller_action >if request.post? > # Process post data as the user has submitted the form. >else ># Display form >end > end > >

[Catalyst] How to detect if the current form request is a post?

hi all In Ruby we can detect if the current form's request is a post or not. def controller_action if request.post? # Process post data as the user has submitted the form. else # Display form end end Looking at Catalyst::Request (http://search.cpan.org/~mramb

Re: [Catalyst] Catalyst 5.8 NEXT deprecated warnings

On Tue, Mar 31, 2009 at 12:52:53PM +0100, Anthony Gladdish wrote: > Catalyst::Plugin::Session::Store::DBIC is trying to use NEXT, which is > deprecated. Please see the Class::C3::Adopt::NEXT documentation for > details The svn version of Session-Store-DBIC is already converted to MRO::Compat. Not

Re: [Catalyst] Catalyst 5.8 NEXT deprecated warnings

Anthony Gladdish wrote: Does anyone know if these plugins are to be updated/fixed to remove this dependency on NEXT, or if there is a recommended work around? Yes, they are, people have been converting things as they've cared about them. As you seem to care about these two, I think you just v

[Catalyst] Catalyst 5.8 NEXT deprecated warnings

Hi, Testing my cat apps tests against Catalyst 5.8. Getting following warnings: Catalyst::Plugin::Session::Store::DBIC is trying to use NEXT, which is deprecated. Please see the Class::C3::Adopt::NEXT documentation for details Catalyst::Plugin::Authorization::ACL is trying to use NEXT, which

Re: [Catalyst] Catalyst LDAP SASL

Walter Vargas wrote: I'm working with *Catalyst::Authentication::Store::LDAP and Catalyst::Model::LDAP*, but i dont want use SSL, i want use SASL how to do that ? Neither of these support SASL, but it would be easy to add. Net::LDAP->bind($dn, password => 'password'); # What happens currentl

Re: [Catalyst] DELETE through REST and Jemplate

J. Shirley wrote: > On Mon, Mar 30, 2009 at 10:31 AM, Emmanuel Quevillon > wrote: > > J. Shirley wrote: > > On Mon, Mar 30, 2009 at 7:39 AM, Emmanuel Quevillon > mailto:t...@pasteur.fr> > >> wrote