>From the documentation, the "Controller" represents an input to the model, and the "View" is an output. In the context of an RESTful web app, I would map an processed HTTP request (GET/POST/etc) to Controller, and rendered HTML/JSON as view.
However, real life web app would need much more than that. Often they need additional IO. Say I need to make use of some 3rd party web service. Then I would need to send some http request. This request I send is an output of my model, but I can hardly call it a "View". How would I deal with situations like this with mvc library? Other additional IOs like logging, state persistence also don't fit into the mvc concept very well. How can we add these features? -- You received this message because you are subscribed to the Google Groups "Haskell Pipes" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
