=encoding utf8 =head1 NAME PEF::Front - B

erl Bffective Web Bramework =head1 SYNOPSIS # startup.pl use MyApp::AppFrontConfig; use PEF::Front::Preload qw(no_db_connect); use PEF::Front::Route ('/' => '/appIndex'); PEF::Front::Route->to_app(); # MyApp::AppFrontConfig.pm package MyApp::AppFrontConfig; sub cfg_no_nls { 1 } sub cfg_no_multilang_support { 1 } 1; # $project_dir/templates/index.html some Template-Toolkit style template. =head1 DESCRIPTION PEF::Front is a Perl web framework with following features. =over =item B You just write API of your application and it's automatically exposed as AJAX or data retrieving methods in your templates. HTML templates can be programmed separately. =item B HTML templates can be programmed by other people who know nothing about Perl. =item B Your API calls are described in YAML files. There're can be set default values, complex parameter checks, input parameter filters, output filters and other things. HTML/AJAX developer can look into these YAML files to understand backend API. =item B Thanks very comprehensive parameter checks, passed into handler request is already checked and filtered, you don't need to make additional validation. =item B Different output filters can be applied to the same data to get different data representation. Input data can be obtained automatically from session, headers, cookies, form and other sources. Results from handlers can set or unset headers or cookies. All this is described in YAML and all these rules are compiled into native Perl code. =item B Request routing is very powerful and effective. Your routing rules are compiled into native Perl code. =item B There're many configurable parameters and functions. They have some sensible defaults that you have to configure only small part of them. It's very easy to configure them in your own *::AppFrontConfig module. =item B PSGI is very effective protocol for passing incoming requests into application. You can use PEF::Front with any PSGI-server. I use L. It is also very wise to have some reverse-proxy server in front of PSGI-server for static content. I use L. =item B PEF::Front has many components that a really useful for typical web applications: =over =item Sessions Session data can be automatically loaded during request validation. =item Oauth2 There're components to easily make authorization on your site for B, B, B, B, B, B, B and B users. =item Localization support There's a message translation support in templates and handlers and automatic language detection based on URL, HTTP headers and Geo IP. =item Captcha Captcha check during request validation. Simple captcha component. Custom captcha image generation is possible. =back =item B Basically these technologies require some event loop architecture to reduce overhead on every connection. But it requires non-trivial callback code for series of complex queries to DB. It is possible to make in quite "usual" code using L + L environment with L for pool of asynchronous Ls. Thre's even L ORM that supports such a pool of connectors. B are available as external modules. =back =head1 Your Application =head2 Project structure Typical directory structure of Your application is alike: + $project_dir/ + $app/ + $Project/ - AppFrontConfig.pm + InFilter/ + OutFilter/ + Local/ + bin/ - startup.pl + model/ + templates/ + var/ + cache/ + captcha-db/ + tt_cache/ + upload/ + www-static/ + captchas/ + images/ + jss/ + styles/ You can redefine almost everything here except B, B and B directories. =head3 What is what =over =item bin Different executables. startup.pl is one of them. Actually this file can have any name that is known to PSGI-server. =item $app Directory of main application code and AppFrontConfig.pm module. Framework determines it automatically from path to loaded AppFrontConfig.pm module. =item $Project Directory structure of application modules. =item InFilter Optional modules for input data validation. =item OutFilter Optional modules for transformation of output data. =item Local Incoming request handlers. =item model YAML-files with descriptions of model methods. Every file describes one method. =item templates Directory of templates. Currently only Template-Toolkit style is supported. =item var/cache Session data and cached responses of handlers. =item var/captcha-db Database for generated captchas. =item var/tt_cache Cache of compiled templates. =item var/upload Root directory for uploaded files. =item www-static Directory of static content. This is typically served by some fast web-server like L. =item www-static/captchas Directory of generated captcha images. This is typically served by the same web-server for static content. =back =head2 Minimal application Minimal application can consist of only two files: B and B. It would look like this: # MyApp::AppFrontConfig.pm package MyApp::AppFrontConfig; sub cfg_no_nls { 1 } sub cfg_no_multilang_support { 1 } 1; # startup.pl use MyApp::AppFrontConfig; use PEF::Front::Response; use PEF::Front::Route; PEF::Front::Route::add_route( get '/' => sub { PEF::Front::Response->new(headers => ['Content-Type' => 'text/plain'], body => 'Hello World!'); } ); PEF::Front::Route->to_app(); You have to define minimal config and routes. Routes can return HTTP response directly. =head1 More information There're guides and demos. =over =item L =item L =item L =item L =item L