On Dec 2, 2008, at 1:47 PM, baaz wrote: > Clearly, the data I should show in these two cases is different, so > the controller code should handle this somehow. > The "create" action in the controller is even messier, redirecting to > different URLs depending on where we came from, etc. These dual-duty > controllers will be bloated and not nice.
I think you nailed it on the head yourself, sounds like two different resources to me. Regardless of what the data model looks like on the back end, the exposed resources through the public API are probably going to need separate controllers. Unless I'm misinterpreting what your trying to achieve here. :: Justin Reagor :: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
