Mat Brown wrote: > Your data model layer should not be aware of application state (or even > assume it is part of a web app). So, this should be done from the > controller/view layer.
More regards to this: I am *deathly afraid* of communicating with web services during my apps' request/response cycles; you have no idea how long it will take for the service to respond back to you, and when something with the service goes wrong (after possibly minutes of waiting), it tends to go wrong in completely unexpected and magical ways (often you'll not even *get* a timeout!). Doing this kind if ish in a background service is trivial if this logic already exists in a model; its impossible if the logic is in a controller. -- Posted via http://www.ruby-forum.com/. -- 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.
