Steve Hay wrote:
Thomas Klausner wrote:
Hi!
On Mon, Sep 08, 2003 at 04:51:55PM +0100, Steve Hay wrote:
The project is going to be written as a series of mod_perl handlers
- one for the main home page, and others for various
sub-components. Each handler is implemented by a separate module
Marc Slagle wrote:
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
Perrin Harkins wrote:
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
/myproject/images [static]
/myproject/javascript [static]
petersm wrote:
Steve Hay [EMAIL PROTECTED] wrote
Location /myproject
SetHandler perl-script
PerlHandler MyProject-dispatcher
/Location
LocationMatch ^/myproject/(images|javascript|stylesheets)
SetHandler default-handler
/LocationMatch
Correct me if I'm wrong, but can't you just
On Tuesday 09 September 2003 11:16, Steve Hay wrote:
Those were actually my very frist ideas, but I decided that I prefer
to have all the URL's to begin with /myproject. I don't necessarily
require that URL to be related to the filesystem structure, but I
just want all the URL's (dynamic and
Hi!
On Tue, Sep 09, 2003 at 10:05:43AM +0100, Steve Hay wrote:
Location /myproject/css
SetHandler default
/Location
Location /myproject/img
SetHandler default
/Location
This is working as expected, i.e. request for /css/foo.css or /img/bar.png
are not handled by Apache::Dispatch
Steve Hay [EMAIL PROTECTED] wrote
Thanks for the idea, though. If I manage to overcome my
inexplicable aversion to file extensions then it certainly looks
like the simplest solution.
I understand the argument that it's better for the user to not know the
extension of the file they are
On Tue, 2003-09-09 at 05:00, Steve Hay wrote:
As in a PerlTransHandler, yes?
Yup.
Is there a performance penalty with this? You're using Perl code to
inspect the URI, and then handing control back to the Apache core if it
is a static file. I wanted to avoid requests for static files
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2
Hi!
On Mon, Sep 08, 2003 at 04:51:55PM +0100, Steve Hay wrote:
The project is going to be written as a series of mod_perl handlers -
one for the main home page, and others for various sub-components.
Each handler is implemented by a separate module (all sub-classes of a
common base
Steve Hay [EMAIL PROTECTED] wrote
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
/myproject/images [static]
/myproject/javascript [static]
/myproject/stylesheets [static]
12 matches
Mail list logo
