NYCPHP Meetup

[csnyder]

On Dec 12, 2007 12:11 AM, inforequest <1j0lkq002 at sneakemail.com> wrote:

> If anyone is enjoying reliable, manageable, strict and pretty URLs on
> one of the "modern frameworks" I'd like to hear about it. That means
> content level control of "pretty" URLs, ability to manage redirection
> (at the content level), and enforced one-URL-per-document.
>
> At this point I'm all in favor of a neutral bolt-on rewrite router.

John, I can't believe you don't have something like this. You've been
asking for it for a few years, so the requirements must not be as
simple as they sound.

Maybe it's a wiki-like version of a reverse proxy. This app would act
as a reverse proxy for your site, so whenever someone requests a url,
the app rewrites it, fetches and lightly caches the content, and
returns it as a response.

Whenever you (as editor) visit a url that doesn't exist, an interface
kicks in that helps you map it to a resource in your site (or create a
redirect to a different url). Since you require one-url-per-resource,
the app would also add a redirect that sends a direct request for the
mapped resource to the pretty url.

Upside is that it would act as a caching/mirroring layer and improve
scalability. Downside is that for some legacy apps, using a reverse
proxy can involve non-trivial amounts of content rewriting and reverse
engineering.

-- 
Chris Snyder
http://chxo.com/