October 2010 - dancer-users - lists.preshweb.co.uk

Re: [Dancer-users] applying the same setting to different routes in different packages
by P Kishor 05 Oct '10

05 Oct '10

On Tue, Oct 5, 2010 at 1:53 AM, Alexis Sukrieh <sukria(a)sukria.net> wrote: > On 05/10/2010 00:04, P Kishor wrote: .. > >> Since Dancer doesn't support the concept of creating a base class, and >> then inheriting from it, how do I apply same settings to any route in >> any package or sub-package? > > Who told you you can use inheritance with Dancer packages? Dancer does > nothing for you regarding inheritance, but that doesn't mean you can't do it > yourself: > > > package FooApp::Base; > > use strict; > use warnings; > > use Dancer ':syntax'; > > sub opts { > return { base => 42 }; > } > > get '/' => sub { > "base opts : ".to_yaml(opts()); > }; > > 1; > > package FooApp::Forum; > > use strict; > use warnings; > use Dancer ':syntax'; > > use FooApp::Base; > use base 'FooApp::Base'; > > sub opts { > my $self = shift; > my $parent_opts = $self->SUPER::opts(); > return { > %{ $parent_opts }, > forum => 34, > }; > } > > get '/' => sub { > "forum opts : ".to_yaml(FooApp::Forum->opts()); > }; > > Tested with Dancer 1.1901 here, working. > > Hope that helps, This is great news, as it will greatly simplify my application. However, it doesn't work for me (also on 1.1901). My app structure is app.pl lib/ app.pm app/ app1.pm in app1.pm, I have ---- package app::app1; use Dancer ':syntax'; use lib ('/Users/punkish/Sites/app/lib'); use app; # do I really need this and the line just above it? use base 'app'; sub opts { my $self = shift; my $opts = $self->SUPER::opts(); return { %{ $opts }, app1 specific opts } }; ---- and, I get the following runtime error Can't call method "SUPER::opts" on an undefined value at /Users/punkish/Sites/app/lib/app/app1.pm line 16. /Users/punkish/Sites/app/lib/app/app1.pm around line 16 13 14 sub opts { 15 my $self = shift; 16 my $opts = $self->SUPER::opts(); 17 18 return { 19 %{ $opts }, > > -- > Alexis Sukrieh > -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

2 3

applying the same setting to different routes in different packages
by P Kishor 05 Oct '10

05 Oct '10

A stylistic question, perhaps a strategy question. This is what I do right now - foo.pl --- use Dancer; .. load_app 'foo'; dance; ---- - foo.pm --- load_app 'foo:bar', prefix => '/bar'; load_app 'foo:baz', prefix => '/baz'; get '/' => sub { template 'index', opts(); }; sub opts { return { various settings; 'logged_in' => session->{logged_in} ? 1 : 0; } } ---- - foo/foo.pm --- get '/' => sub { template 'index', opts(); }; sub opts { return { various settings; 'logged_in' => session->{logged_in} ? 1 : 0; } } ---- - foo/bar.pm --- get '/' => sub { template 'index', opts(); }; sub opts { return { various settings; 'logged_in' => session->{logged_in} ? 1 : 0; } } ---- While some of the "various settings" are different in the different packages, some of them are the same. Definitely, 'logged_in' is the same across all the packages, so I want to set it only in one place. Since Dancer doesn't support the concept of creating a base class, and then inheriting from it, how do I apply same settings to any route in any package or sub-package? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

2 1

Tokens and Template plugins
by Mike Schroeder 05 Oct '10

05 Oct '10

I'm a new Dancer user, but I'm loving it so far. In 4 days I was able to learn dancer, create plugins for accessing our existing APIs, session management and authentication, and port a relatively complex application. Dancer is elegantly simple. Thanks for a great architecture. Now for my question: Since the app I was porting used HTML::Template, I decided to use the Dancer::Template::HtmlTemplate module contributed by David Precious. It nicely renders the tokens passed in, however I believe HTML::Template expects a Hash Ref made up of either scalars or of Array of Hash - something to the effect of: { PARAM => 'value', PARAM2 => 'value', LOOP_PARAM => [ { PARAM => VALUE_FOR_FIRST_PASS, ... }, { PARAM => VALUE_FOR_SECOND_PASS, ... } ... ], ANOTHER_LOOP_PARAM => [ { PARAM => VALUE_FOR_FIRST_PASS, ... }, { PARAM => VALUE_FOR_SECOND_PASS, ... } ... ] } However, Dancer::Helpers::template() passes the settings, session, request and params as a Hash of Hash - making the vars inaccessible to HTML::Template. $tokens ||= {}; $tokens->{settings} = Dancer::Config->settings; $tokens->{request} = Dancer::SharedData->request; $tokens->{params} = Dancer::SharedData->request->params; if (setting('session')) { $tokens->{session} = Dancer::Session->get; } I think there are two approaches: 1) Dancer::Template::HtmlTemplate needs to be smart enough to fix up the $tokens hash to reformat those default values into something visible to HTML::Template - *something* like: foreach my $kind ( qw( settings request params session ) ) { foreach my $key ( keys %{ $tokens->{$kind} } ) { $tokens->{$kind.'-'.$key} = delete $tokens->{$kind}->{$key}; } } 2) an alternate solution would be to make the creation of tokens a subroutine that a Template plugin can expose back to Dancer as an alternative way of serializing the tokens for the given Template engine. *something like: $tokens ||= {}; if (Dancer::Template->engine->can('create_default_tokens') ) { $tokens = Dancer::Template->engine->create_default_tokens($tokens); } else { $tokens->{settings} = Dancer::Config->settings; $tokens->{request} = Dancer::SharedData->request; $tokens->{params} = Dancer::SharedData->request->params; if (setting('session')) { $tokens->{session} = Dancer::Session->get; } } If I am missing something really obvious, my apologies in advance. Assuming this *is* a legitimate issue, which way is the preferred solution? Mike.

2 2

deployment help
by P Kishor 04 Oct '10

04 Oct '10

I have been using my multiple Dancer apps with Apache2 CGI, but want to move to a persistent web environment. I had some issues with Apache2/mod_perl where sessions from different Dancer apps were colliding, but that may be solved with the help of a recent post by Alexis (prefix my sessions with app names). So, I have started testing my apps under Apache2/mod_perl, but find that to be be fairly slow in response and quite high in memory consumption. Am looking for advise on speeding up Apache. Should I be using mod_psgi? Is that mature and stable enough to use? Perhaps I am looking for advise here for alternatives as well (the problem is, at least one of my applications uses CGI, so I have to have CGI support). I have been considering nginx, as I have heard good things about it. The Dancer::Deployment pod mentions using nginx, but only as a proxy server to a `perl dancer` process. I don't really want to do that as multiple apps means multiple perl processes running all the time on my web server. Are there any tutes or docs on using nginx with embedded perl or some other persistent perl process to power Dancer? Does anyone have any other suggestion? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

2 2

Pass to own request
by igor.bujna＠post.cz 03 Oct '10

03 Oct '10

Hi, I'm found in documentation 'pass' function which make procesing of next request. But i want in some my code to put other request but request not from next matching route. Something like that: get '/index' => sub { ....... }; get '/some/route' => sub { if (...) { # How can I put this code to '/index' route not use redirect. } } Thank for yours answer and sorry for my english :( I must learn

2 2

protecting some routes, not other
by P Kishor 02 Oct '10

02 Oct '10

I am looking at the Cookbook recipe for implementing a session based login mechanism. ---- before sub { if (! session('username') && request->path_info !~ m{^/login}) { var requested_path => request->path_info; request->path_info('/login'); } }; get '/login' => sub { # Display a login page; the original URL they requested is available as # vars->{requested_path}, so could be put in a hidden field in the form }; ---- What I really want is to declare, in one place, the routes that should be protected, the rest being openly accessible, or vice versa, that is, declare the routes that should be accessible freely without login, the rest requiring a login. What is the best way to do that? An extension of this requirement would be to decralre an entire sub application to be protected with the use of the prefix. I am thinking of something like before sub { if (! session('username') && request->path_info !~ m{^/login} && <******>) { var requested_path => request->path_info; request->path_info('/login'); } }; The logic would go in the <*******> part, something like (route in (array of protected routes)) Is the route available in a variable? or, is it only accessible via regexp? Has this been solved already? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

1 0

Problem with using the prefix feature to split the application
by P Kishor 02 Oct '10

02 Oct '10

I was using the following idiom, and everything was working fine ---- package app; use Dancer ':syntax'; use Dancer::Plugin::Ajax; load_app "app::app1", prefix => "/app1"; load_app "app::app2", prefix => "/app2"; .. true; ---- package app::app1; use Dancer ':syntax'; .. true; ---- package app::app2; use Dancer ':syntax'; .. true; ---- The above was a holdover from earlier versions of Dancer, but, as I noted above, it was working fine. Today I noticed that the Dancer::Cookbook has a different suggestion, so I implemented that and ran into a problem. My new implementation is ---- package app; use Dancer ':syntax'; use Dancer::Plugin::Ajax; use app::app1; use app::app2; prefix undef; .. true; ---- package app::app1; use Dancer ':syntax'; prefix 'app1'; .. true; ---- package app::app2; use Dancer ':syntax'; prefix 'app2'; .. true; ---- I get the following error Error while loading /Users/punkish/Sites/app/app.pl: unable to load application app : not a valid prefix: `app', must start with a / at /usr/local/lib/perl5/site_perl/5.12.1/Dancer/App.pm line 32., referer: http://app.local/app1/ What gives? -- Puneet Kishor

2 3

Template layout
by igor.bujna＠post.cz 02 Oct '10

02 Oct '10

Hi, i now read every documentation about parameters to 'template' and there is, for disable layout I make this one: template 'index.tt', {}, { layout => undef }; Standart use standart layout from config.yml. My idea, is use for some request own or other layout. Now must be some hack to change $app->setting{layout}. I think there was simplest way when you put this my patch. Now in parameter in template, you can use own layout in layout directory. Such as use views/layouts/simple.tt template 'index.tt', {}, { layout => 'simple'}; --- Helpers.pm~ 2010-10-02 14:16:14.000000000 +0200 +++ Helpers.pm 2010-10-02 14:17:06.000000000 +0200 @@ -34,9 +34,8 @@ my $app = Dancer::App->current; - $options ||= {layout => 1}; - my $layout = $app->setting('layout'); - undef $layout unless $options->{layout}; + $options ||= {}; + my $layout = exists($options->{layout} ? $options->{layout} : $app->setting('layout'); $tokens ||= {}; $tokens->{settings} = Dancer::Config->settings;

1 0

a few unresolved issues
by P Kishor 02 Oct '10

02 Oct '10

I have the following unresolved issues that seems to have gotten Warnocked [1]. [1] http://en.wikipedia.org/wiki/Warnock's_Dilemma subject: status code needs to be an integer greater than or equal to 100 link: http://www.backup-manager.org/pipermail/dancer-users/2010-October/000369.ht… sent: Fri Oct 1 04:01:28 CEST 2010 subject: Use of uninitialized value $val link: http://www.backup-manager.org/pipermail/dancer-users/2010-October/000368.ht… sent: Fri Oct 1 00:02:02 CEST 2010 subject: croaks on utf-8 sent: Wed Sep 22 13:28:39 CEST 2010 link: http://www.backup-manager.org/pipermail/dancer-users/2010-September/000353.… subject: Session collision of multiple web sites with Plack::Handler::Apache2 link: http://www.backup-manager.org/pipermail/dancer-users/2010-September/000338.… sent: Mon Sep 13 04:29:52 CEST 2010 The first and the last one are particularly important. The first has stopped me in my tracks completely, and the last is resulting in very slow web sites. Any help would be appreciated. Many thanks. I am using the latest build of Dancer, 1.9x -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

4 3

status code needs to be an integer greater than or equal to 100
by P Kishor 01 Oct '10

01 Oct '10

I am getting the following error "status code needs to be an integer greater than or equal to 100 at /usr/local/lib/perl5/site_perl/5.12.1/Plack/Middleware/StackTrace.pm line 27" I am assuming it is coming from 103: unless ($res->[0] =~ /^\d+$/ && $res->[0] >= 100) { in Carp::croak at /usr/local/lib/perl5/site_perl/5.12.1/Plack/Middleware/Lint.pm line 103 Why am I encountering this? Is this a timeout? -- Puneet Kishor

1 1