My controllers have gotten unwieldy. The situation looks well-suited to the use of the MVP pattern but the latest links Google is giving me are from '07. Looks like there was some pretty good discussion that just fell off a cliff. Has someone come up with a better solution?
A little background on my situation in case it helps and you're still reading ;-) What was initially envisioned as a fairly typical Rails application with a heavy dose of RJS has grown into a soon-to-be RESTful (or soon will be) Rails web service that talks to two Ajax clients, one a single-page and the other a multipage app, and two self-spawned HTTP clients. Each of the clients is pretty-well constrained in terms of the resources / methods it needs. I'm thinking of moving the Ajax clients to using an MVP pattern and keeping the HTTP clients on the standard Rails MVC pattern. My thought is that if each client is restricted to one 'channel' (HTML | JS | XML) then I'll not only get better structure / testability on the code serving the Ajax clients, from a security perspective, I can lock down resources by URL, HTTP verb, and protocol. Any thoughts / discussion is much appreciated. Best regards, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
