Mailing List Archive

I'd try a regexp in my begin action.
But I'd first look at something more properly restful
http://www.pausetosee.com/prn/n7ivdbdq8808p
You can also do pre-dispatching with rewrite rules on your webserver.
in apache
Rewrite Engine On
RewriteRule ^/prn(.*)
/http://localhost:3003/controllers/people/n7ivdbdq8808p [P]


On 10/03/2013 09:41 PM, bill hauck wrote:
>
> I've been struggling with the best way to accomplish a somewhat simple
> task: direct to a specific controller/action based on a code in the uri.
>


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Hit send too soon
RewriteRule ^/prn(.*) /http://localhost:3003/controllers/people/$1 [P]



On 10/03/2013 10:13 PM, John Karr wrote:
> I'd try a regexp in my begin action.
> But I'd first look at something more properly restful
> http://www.pausetosee.com/prn/n7ivdbdq8808p
> You can also do pre-dispatching with rewrite rules on your webserver.
> in apache
> Rewrite Engine On
> RewriteRule ^/prn(.*)
> /http://localhost:3003/controllers/people/n7ivdbdq8808p [P]
>
>
> On 10/03/2013 09:41 PM, bill hauck wrote:
>>
>> I've been struggling with the best way to accomplish a somewhat
>> simple task: direct to a specific controller/action based on a code
>> in the uri.
>>
>


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

> Any suggestions on how to do this? I'm toying with a large switch statement in the root controller and visiting the appropriate controller/action based on the parameter. Is this right? Does Catalyst provide a way to accomplish this either easier or cleaner?

Hi Bill,

Rather than a big mess of a switch statement, I would be inclined to construct a hash that contains the rules for the mapping of the short-codes to the appropriate Controller/action, i.e.

my $codes = {
'tms' => [ 'Controller1', 'action1' ],
'tve' => [ 'Controler1', 'action2' ],
'prn' => [ 'ControllerN', 'actionN' ],
};

then the control flow is more or less abstracted into a simple hash of rules:

if($args[0] =~ /^(\w{3})(\w{13})$/){ # separate media type from key
my ($code, $key) = ($1, $2);
if(my $ca = $codes->{$code}){
$c->forward("MyApp::Controller::".$ca->[0], $ca->[1], [ $key, @args ]);
}
else {
...
}
}

To be honest, I think this is the sort of use for which the 'Regex' action type shines, but I believe it's being deprecated.

cheers
RET
_______________________________________________________________
If the programmers like each other, they play a game called "pair programming".
And if not, then the game is called "peer review".
- Anna Nachesa (@ashalynd)

Richard Thomas




_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

You could also try to encapsulate the match logic in an action class or role.  --jnap



On Saturday, October 19, 2013 1:58 AM, Richard Thomas <ret@mac.com> wrote:
> Any suggestions on how to do this?  I'm toying with a large switch statement in the root controller and visiting the appropriate controller/action based on the parameter.  Is this right?  Does Catalyst provide a way to accomplish this either easier or cleaner?

Hi Bill,

Rather than a big mess of a switch statement, I would be inclined to construct a hash that contains the rules for the mapping of the short-codes to the appropriate Controller/action, i.e.

my $codes = {
    'tms' => [ 'Controller1', 'action1' ],
    'tve' => [ 'Controler1', 'action2' ],
    'prn' => [ 'ControllerN', 'actionN' ],
};

then the control flow is more or less abstracted into a simple hash of rules:

if($args[0] =~ /^(\w{3})(\w{13})$/){ # separate media type from key
    my ($code, $key) = ($1, $2);
    if(my $ca = $codes->{$code}){
        $c->forward("MyApp::Controller::".$ca->[0], $ca->[1], [ $key, @args ]);
    }
    else {
        ...
    }
}

To be honest, I think this is the sort of use for which the 'Regex' action type shines, but I believe it's being deprecated.

cheers
RET
_______________________________________________________________
If the programmers like each other, they play a game called "pair programming".
And if not, then the game is called "peer review".
- Anna Nachesa (@ashalynd)

Richard Thomas





_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/