A project that I'm working on requires mix-and-mash of dynamic and
static content delivered from the same base path. My first priority
was not speed/performance, but flexibility and control. To be more
specific - in my case Catalyst-based application is the one that
decides, based on misc BL,
Hi,
On Aug 14, 2007, at 9:42 PM, Alejandro Imass wrote:
IMHO you should let each component do what it does best. Web servers
are specialized for static content so le IT do this work. Your app is
specialized in dyn content so let IT do the work.
Of course, but your solution is the standart
perlbal looks pretty interesting, but not much online docs. anyone
using it with catalyst?
at the moment I'm happy with lighty, but might be useful for the future.
--
Daniel McBrearty
email : danielmcbrearty at gmail.com
http://www.engoi.com
http://danmcb.vox.com
http://danmcb.blogger.com
IMHO you should let each component do what it does best. Web servers
are specialized for static content so le IT do this work. Your app is
specialized in dyn content so let IT do the work.
Here is an example apache2 conf to handle cat / static content. In
this app, both standard cat static
On Sun, Aug 12, 2007 at 03:49:40PM -0400, Andy Grundman wrote:
On Aug 12, 2007, at 2:22 PM, Peter Lytle wrote:
Good afternoon - I am working on a Catalyst application that serves
dynamic website content for multiple sites, and I've run into some
difficulty about static content. Each
On Aug 13, 2007, at 7:08 AM, Matt S Trout wrote:
Did we make _serve_static_file public yet? Having a way to do
something
like that dynamically is the one thing I still -really- miss from
the old
Static plugin.
... alternatively, we could always have Controller::Static blah
blah plugins
Hi,
On Aug 12, 2007, at 8:59 PM, [EMAIL PROTECTED] wrote:
On 8/12/07, Peter Lytle [EMAIL PROTECTED] wrote:
If someone has a solution from the Apache side, that's fine but I
suspect that it might be
easier to do this with Catalyst::Plugin::Static::Simple
Don't serve static content through
On 8/12/07, Peter Lytle [EMAIL PROTECTED] wrote:
If someone has a solution from the Apache side, that's fine but I suspect
that it might be
easier to do this with Catalyst::Plugin::Static::Simple
Don't serve static content through perl. Let your webserver do it.
Usually people just set up
On Aug 12, 2007, at 2:22 PM, Peter Lytle wrote:
Good afternoon - I am working on a Catalyst application that serves
dynamic website content for multiple sites, and I've run into some
difficulty about static content. Each website has unique static
content (images, css, rss) and I am
On 8/12/07, Peter Lytle [EMAIL PROTECTED] wrote:
If someone has a solution from the Apache side, that's fine but I
suspect that it might be
easier to do this with Catalyst::Plugin::Static::Simple
Don't serve static content through perl. Let your webserver do it.
Usually people just set
On 8/12/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
a lot of times, 'static' content is found via database queries. and
sometimes that content needs to be protected from unauthorized viewers,
and your authorization mechanisms are already built into your application,
so you can't just use
11 matches
Mail list logo
