>Jonathan Lonsdale wrote:
>> 2. Distinct content handlers each with their own Location directive.
Could
>> be a pain to maintain the server config.
In my company we wanted an application which would make it easy to give
users shared access to data that changed occasionally. The initial
request wa
On Sun, 18 Aug 2002, Jonathan Lonsdale wrote:
> Here's a few approaches I thought of:
In a previous life[1] I made a system that was configured like
my $site1 = new Foo::Site(site => 'www.example.com');
$site1->register_handler(
new Foo::ImageHandler(path => '/images/', format => 'png'
Greetings.
> People often seem to get bent out of shape about putting a
> few Location directives in httpd.conf,
I suspect that it may be due to the intimidating length that httpd.conf has
reached in these times. I found that separating customizations in breakaway
'Include'd .conf files - and
Jonathan Lonsdale wrote:
> 2. Distinct content handlers each with their own Location directive. Could
> be a pain to maintain the server config.
You would typically have a single handler that covers one "application"
with many screens, so instead of having an entry there for every
template you
On Sun, Aug 18, 2002 at 12:31:03AM +0100, Jonathan Lonsdale wrote:
> I'm curious to know how people approach application development with
> mod_perl in situations where there could be dozens of distinct
> screens/interfaces. I'm currently using the HTML::Template system.
When using HTML::Template
Chris Winters <[EMAIL PROTECTED]> wrote:
>On Sat, 2002-08-17 at 19:31, Jonathan Lonsdale wrote:
>> I'm curious to know how people approach application development with
>> mod_perl in situations where there could be dozens of distinct
>> screens/interfaces. I'm currently using the HTML::Template sy
On Sat, 2002-08-17 at 19:31, Jonathan Lonsdale wrote:
> I'm curious to know how people approach application development with
> mod_perl in situations where there could be dozens of distinct
> screens/interfaces. I'm currently using the HTML::Template system.
>
> Here's a few approaches I thought
On Sun, 18 Aug 2002, Jonathan Lonsdale wrote:
> Date: Sun, 18 Aug 2002 00:31:03 +0100
> From: Jonathan Lonsdale <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Mod_perl Application Development
>
> I'm curious to know how people approach application d
[mailto:[EMAIL PROTECTED]]
Envoyé : dimanche 18 août 2002 01:31
À : [EMAIL PROTECTED]
Objet : Mod_perl Application Development
I'm curious to know how people approach application development with
mod_perl in situations where there could be dozens of distinct
screens/interfaces. I'm
I'm curious to know how people approach application development with
mod_perl in situations where there could be dozens of distinct
screens/interfaces. I'm currently using the HTML::Template system.
Here's a few approaches I thought of:
1. Single monolithic content handler. Could be hard to main
10 matches
Mail list logo
