Return-Path: X-Original-To: apmail-perl-modperl-archive@www.apache.org Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AFADB6D16 for ; Mon, 4 Jul 2011 16:43:53 +0000 (UTC) Received: (qmail 71739 invoked by uid 500); 4 Jul 2011 16:43:52 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 71695 invoked by uid 500); 4 Jul 2011 16:43:51 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 71688 invoked by uid 99); 4 Jul 2011 16:43:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 16:43:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.97.132.202] (HELO homiemail-a72.g.dreamhost.com) (208.97.132.202) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 16:43:43 +0000 Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id 79B796B0079 for ; Mon, 4 Jul 2011 09:43:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=bac2bac.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=bac2bac.com; b=kkpKJ9fl6i9b/Sixq8r8Two9gPzN2bRDIW7iXEelDUbSdA0qAB8IPETwAG1om ahgrBdRO0VnEn/suOuihI4eEpL3488fwjvx7vAljmyqrs2yruxriTUXuhTveUVjU kaUzceLEjTfBjgl4CeOTVDJcBQONTmA2Bgpytwk1GO5eAA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bac2bac.com; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=bac2bac.com; bh=qQbYz zVRYVUYy4iVte2zJZroLGM=; b=LIQjXDp6n3kxKrm5ixG08IHBI3OiNkfLLg5cE u8zJg07aTw7THBXdeoWzNREIIdvynXsei/7bXalvQYRBCr56MlG8Q1SYcS73hRp8 PVz3yO3TK6/2fOYtS9qmfk2TJTU9n1MELOYEdoCgKnySP1GUlPGHo+xB8c6RYihV kCCLnA= Received: from [127.0.0.1] (71-20-23-132.war.clearwire-wmx.net [71.20.23.132]) (Authenticated sender: bac2bac@bac2bac.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPA id 020636B0070 for ; Mon, 4 Jul 2011 09:43:21 -0700 (PDT) Message-ID: <4E11ED98.8070303@bac2bac.com> Date: Mon, 04 Jul 2011 09:43:04 -0700 From: gAzZaLi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: modperl@perl.apache.org Subject: Re: How do you use mod_perl for your web application? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 6/15/2011 9:01 PM, Fred Moyer wrote: > I'm interested in hearing about what application frameworks (Catalyst, > CGI::App, Mojolicious) are used here with mod_perl. Given the number > of emerging Perl based webservers on CPAN (in addition to Nginx, > lighty, etc), it seems like there are many more Perl web application > and webservers out there now than there were five years ago. One-page app. using Ajax/JSON. Server side is mod_perl 2.x, Apache (configured variously for proxy, static content and mod_perl) and MySQL. Code is OO and uses persistent objects. No frameworks or much use of CPAN modules other than DBI. Cient interface is assembled entirely on client, using JavaScript and DOM. This frees up server from having to do any interface generation. Regardless of request type (POST/GET etc), the server response is in the form of JavaScript object(s) (really just a plain text string), which is 'eval'ed by JavaScript on the client.