good question. I also would like to see some discussion on this. I'm not certain but it seems that some feel that REST implies CRUD. Some resources do map that way but not all and even when they do, I rarely want all of those operations exposed. I end up not using resource definitions in my routes because I don't want all the routes exposed most of the time.
I find it easier/safer to incrementally add each route one action at a time. But this may be simply because I'm not enlightened ;). thanks, Jon On Dec 17, 1:36 pm, cult hero <[email protected]> wrote: > Let's say I go ahead and use "resources <resource>" in my router.rb to > create some generic routes for something but I only want a subset of > those routes. (For instance, let's say I don't want to "show" by id, > but rather, by a slug field.) > > Should I create my routes from scratch or is there a good way of > removing a couple of the routes generated by the resources method? I > was thinking you could create a controller that just automatically > raises a NotFound exception, but that seems like a bit of a kludge. > > Part of this question comes from me trying to understand CRUD in merb > but the examples on the wiki all seem to be based around resources > which is adding an extra layer of stuff for me to grok. > > (As a side note, I'm coming from a limited Django background and NOT a > Rails background, so a lot of these conventions are quite a bit more > foreign to me than they might be to others.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
