Mailing List Archive: Apache: Docs

mod_rewrite @ hackathon

Index | Next | Previous | View Threaded

rbowen at rcbowen

Oct 28, 2009, 11:32 AM

Post #1 of 6 (75 views)
Permalink

mod_rewrite @ hackathon

A while back I split the mod_rewrite "guide" into two files, mostly
because the one was way too long.

That was a mistake, since the division between basic and advanced is
pretty arbitrary, and now nobody can find anything.

I'm planning to spend whatever time I have at the hackathon next week
splicing them back together and considering whether a more sensible
division would work - perhaps by topic, or by ... I don't know.
Suggestions welcomed. Yes, I should have started this thread weeks
ago, but it's been pretty busy chez moi, and this is the first day
I've really had time to think about the hackathon.

And I need to work on my mod_perl presentation, too, so the two things
go together pretty well. Ideally, my mod_perl presentation is
something of a rewrite guide style anyways.

--Rich

--
Rich Bowen
rbowen[at]rcbowen.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

niq at apache

Oct 28, 2009, 5:05 PM

Post #2 of 6 (71 views)
Permalink

Re: mod_rewrite @ hackathon [In reply to]

On 28 Oct 2009, at 18:32, Rich Bowen wrote:

> A while back I split the mod_rewrite "guide" into two files, mostly
> because the one was way too long.
>
> That was a mistake, since the division between basic and advanced is
> pretty arbitrary, and now nobody can find anything.
>
> I'm planning to spend whatever time I have at the hackathon next
> week splicing them back together and considering whether a more
> sensible division would work - perhaps by topic, or by ... I don't
> know. Suggestions welcomed. Yes, I should have started this thread
> weeks ago, but it's been pretty busy chez moi, and this is the first
> day I've really had time to think about the hackathon.
>
> And I need to work on my mod_perl presentation, too, so the two
> things go together pretty well. Ideally, my mod_perl presentation is
> something of a rewrite guide style anyways.

I won't be there, but if you're on IRC, I might take an interest in
working
concurrently on "mod_rewrite is obsolete", a guide to often-simpler
alternatives based on the examples in the rewriteguide.

Oh, and it won't show mod_rewrite obsolete in all applications.
Hopefully it'll give readers a much clearer idea of the subset of
current use cases where it is indeed a good option :)

--
Nick Kew

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

mads at toftum

Oct 29, 2009, 3:48 AM

Post #3 of 6 (67 views)
Permalink

Re: mod_rewrite @ hackathon [In reply to]

On Thu, Oct 29, 2009 at 12:05:59AM +0000, Nick Kew wrote:
> I won't be there,

Me neither.

> but if you're on IRC, I might take an interest in
> working
> concurrently on "mod_rewrite is obsolete", a guide to often-simpler
> alternatives based on the examples in the rewriteguide.
>
> Oh, and it won't show mod_rewrite obsolete in all applications.
> Hopefully it'll give readers a much clearer idea of the subset of
> current use cases where it is indeed a good option :)
>
I'm not sure I completely agree on mod_rewrite being obsolete :)
However, I used to use examples of what not to do in mod_rewrite as the
first part of my apachecon mod_rewrite talk. If memory serves me right,
there was five or so examples of things done in mod_rewrite that were
best done elsewhere. I still think they serve as a good way of showing
what mod_rewrite is capable of and I'd be happy to dig them out and add
them to the docs if that'd be any help.
Should we just go ahead and make a "when not to use mod_rewrite guide"?

vh

Mads Toftum
--
http://soulfood.dk

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

mads at toftum

Oct 29, 2009, 4:02 AM

Post #4 of 6 (66 views)
Permalink

Re: mod_rewrite @ hackathon [In reply to]

On Wed, Oct 28, 2009 at 02:32:35PM -0400, Rich Bowen wrote:
> I'm planning to spend whatever time I have at the hackathon next week
> splicing them back together and considering whether a more sensible
> division would work - perhaps by topic, or by ... I don't know.
> Suggestions welcomed. Yes, I should have started this thread weeks
> ago, but it's been pretty busy chez moi, and this is the first day
> I've really had time to think about the hackathon.
>
Just now taking a really quick look at the current guide in 2.2, perhaps
a split could be:

1. redirecting/remapping
2. controlling access
3. when not to use mod_rewrite (see my response to Nick)
3. advanced features

vh

Mads Toftum
--
http://soulfood.dk

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

niq at apache

Oct 29, 2009, 4:20 AM

Post #5 of 6 (66 views)
Permalink

Re: mod_rewrite @ hackathon [In reply to]

On 29 Oct 2009, at 10:48, Mads Toftum wrote:

> On Thu, Oct 29, 2009 at 12:05:59AM +0000, Nick Kew wrote:
>> I won't be there,
>
> Me neither.
>
>> but if you're on IRC, I might take an interest in
>> working
>> concurrently on "mod_rewrite is obsolete", a guide to often-simpler
>> alternatives based on the examples in the rewriteguide.
>>
>> Oh, and it won't show mod_rewrite obsolete in all applications.
>> Hopefully it'll give readers a much clearer idea of the subset of
>> current use cases where it is indeed a good option :)
>>
> I'm not sure I completely agree on mod_rewrite being obsolete :)
> However, I used to use examples of what not to do in mod_rewrite as
> the
> first part of my apachecon mod_rewrite talk.

Yes, I remember that, and your work from back then could be a
nice start to an "is obsolete" doc.

> Should we just go ahead and make a "when not to use mod_rewrite
> guide"?

That's the general idea :)

But my major theme is that we're not just talking about the classics:
mod_alias, or re-inventing content negotiation and getting it wrong
(to be fair, neither was your talk). The common usage that seems
to generate most pain among users if where it gets turned into a
horribly awkward scripting language with the two commands
RewriteCond=Single-IF and RewriteRule=GOTO + side-effects,
which is also obsoleted in trunk.

--
Nick Kew

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

mads at toftum

Oct 29, 2009, 4:25 AM

Post #6 of 6 (65 views)
Permalink

Re: mod_rewrite @ hackathon [In reply to]

On Thu, Oct 29, 2009 at 11:20:17AM +0000, Nick Kew wrote:
> But my major theme is that we're not just talking about the classics:
> mod_alias, or re-inventing content negotiation and getting it wrong
> (to be fair, neither was your talk). The common usage that seems
> to generate most pain among users if where it gets turned into a
> horribly awkward scripting language with the two commands
> RewriteCond=Single-IF and RewriteRule=GOTO + side-effects,
> which is also obsoleted in trunk.
>
When you've got a hammer, everything start looking like a nail.
My primary interest is 2.2 and older - while interesting, I don't think
trunk is worth too much effort just yet ;)

vh

Mads Toftum
--
http://soulfood.dk

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: docs-help[at]httpd.apache.org

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com