Marnen: > you have one application, accessible through multiple channels. > Keep it that way -- since it's one application
Andrew: > One issue with splitting the application into 3 will be > consistency of deployment > You could add something like app/importers and app/exporters > and treat them like "controllers" for the alternate interfaces. These are good points, both of you, and they made me think some more about the layout of my application. What really bothers me is that, right now, all import code is started by executing "script/runner Janitor.perform_daily_tasks", where Janitor is a class defined in the model folder. This means, that the "Janitor code" is automatically loaded by Rails, adding code to each mongrel that has nothing to do with the web interface. I think I will try to convince my colleague, that do the app/importers & app/exporters approach. It seems the right way. Thanks a bunch both of you. - Carsten -- 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 -~----------~----~----~----~------~----~------~--~---
