> Out of curiosity, what is the rationale for wanting to POST to > another controller. We're working on some stuff that'll give you an > object that represents the Resource that you could modify (instead > of touching the ORM directly), which would encapsulate auth, authz, > etags, caching, etc.
I was going to say, it sounds like there must be some sort of actions being taken within the controllers that he wants to access, which aren't reflected in his data models. Otherwise, whatever the controllers are doing outside their normal requirements should be within the business logic, thus instantiate a model class and go at it. :: 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 -~----------~----~----~----~------~----~------~--~---
