Thanks Brian for this! That sounds good! A lot of work, but good, thanks for this!
julien Brian Hogan wrote: > Controllers are designed (in MVC patterns) to process requests and > deliver > responses. Rails-based controllers are designed for HTTP request/ > response. > The answer is to make your own controller that answers your agents' > responses. > > Take advantage of Ruby here - take common code OUT of the controllers > and > put it into modules. Include the modules into your controllers, then > make > your own listener class that also mixes those models in. Use a daemon to > keep that listener going. Railscasts.com has a nice screencast on > daemons. > > How does that sound? > > On Tue, Oct 14, 2008 at 3:50 PM, Julien Genestoux < -- 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 -~----------~----~----~----~------~----~------~--~---
