in reply to Nested Dispatch Tables?

Ditum Ne Agas:   Do Not Do A Thing Already Done.

What you are describing is “a RESTful application,” and there's no good reason to do that yet again. It's already been done. And, done well. Look at things like Catalyst and other existing Perl frameworks which you might be able to apply to your goals.

Programmers “instinctively” jump to the conclusion that they must write a new application, but let's face it:   ain't too much really new in this world, and there's no point in doing yet-again what has already been done. Just hitch a ride on a passing starship and go.

“I don't want to invent a warp engine! I want to get to Alpha Centauri in time for dinner!”

Replies are listed 'Best First'.
Re^2: Nested Dispatch Tables?
by Spidy (Chaplain) on Mar 24, 2008 at 16:26 UTC

    At the core of it, the RESTful interface isn't the overarching goal - it's just a single piece of a larger entity. It doesn't make sense to me to use an entire framework when all I need is a dispatch table. The URL rewriting example was simply to explain that different types/actions would be getting passed to my script.