I am all for increasing the M in the MVC of Yesod. In a simple REST app where resources closely map to the data modeling, this can be less of an issue. Basically you need the M once you would have duplicate model code between any 2 requests. Chris is advocating a fairly strict separation. I think it can still be
simpler to put a read query in a controller. Once that query (or a part
of it) is needed elsewhere it should definitely be named and reused.
Updates do need to maintain invariants and thus should generally stay out of the
controller. I would like to come up with a good system for maintaining
invariants and propagating violations to forms, and other useful systems
for doing more than just taking the query out of the controller.<div><br></div><div>Let us know if there is anything stopping you from separating out code into a Models directory right now.</div><div><br></div><div>Greg Weber</div>
<div><div><div><br><div class="gmail_quote">On Fri, Jun 10, 2011 at 4:00 AM, Aur Saraf <span dir="ltr"><<a href="mailto:sonoflilit@gmail.com">sonoflilit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
None of us should miss this. It especially raised a few questions in<br>
my head about the architecture of my site.<br>
<br>
<a href="http://chrisdone.com/posts/2011-06-05-postgres-hpaste-edsls.html" target="_blank">http://chrisdone.com/posts/2011-06-05-postgres-hpaste-edsls.html</a><br>
<br>
_______________________________________________<br>
web-devel mailing list<br>
<a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
</blockquote></div><br></div></div></div>