I find the RESTful routing very confusing for anything other than the
CRUD mode. I can see how GET/PUT/POST/DELETE maps to the controller for
that. Its been soooooo well documented and soooooo many examples; I’m
almost sick of it.
But many of us aren’t doing the kind of model that is in AWDWR, the
catalogue/invoice type of thing.
There’s a whole class of applications that have a very different front
end" Wikis, Games and so forth. Essentially they have one UI because
there is only the one conceptual model that that the user sees. (The
AWDWR has a catalogue view, a invoice view …).
Something like Instiki has 26 public methods - that is things that can
appear as URLs in buttons. Not all of them fit very obviously into the
I can squint hard and treat the various print and RSS/Atom as special
cases of ‘view’, all I’ve really done, as far as I can see, is made my
menu button code more complicated.
Instiki also has one shortcoming that is easy to get around. Its urls
are of the form
to point to the wiki controller.
For many domains this is unacceptable. Yes, I know it can be cleaned up
with Apache mod_rewrite, but many of us use hosted services and would
rather do it with the application - in routes.
So would those Rails-ists experienced in resourceful techniques please
help out the rest of us and come up with examples and illustrations that
are a little different, that aren’t in the CRUD model, that don’t
require the name of the controller in the URL to do a 1:1 mapping
Please, lets see some flexibility rather than the same old same old
being repeated. Those who do want the CRUD mode - well there’s plenty
out there on the 'Net right now, you don’t need to add to it with “me
Over the last few centuries, mathematicians have demonstrated
a remarkable tendency to underestimate the cryptanalytic powers
of blunt and heavy objects.
– Jamie Reid, CISSP