Carsten Gehling wrote: > I am maintaining a large Rails application, that consists of several > "interfaces": > > 1) The web interface (figures) > 2) Import of data from external providers > 3) Export of data to a large range of customers > > It seems to me quite bloated to have all the code from 2) and 3) inside > the web-application, since they functionally have nothing in common. The > only reason for them being there, is that they also need the business > rules implemented in the models. [...] > ii) Split my current application into 3 seperate applications - each > only containing what is nessecary for its own uses: [...]
I am not 100% sure that I'm correctly understanding the current structure of your app, but if I am, my advice is this: you have one application, accessible through multiple channels. Keep it that way -- since it's one application, it probably shouldn't be broken down any further from the user's point of view. Just keep everything modularized well enough that the interfaces don't have much coupling to the models. (Of course, Phlip is liable to say something totally different, and if he does, you should definitely listen to him, not me.) Best, -- Marnen Laibow-Koser [email protected] http://www.marnen.org -- 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 -~----------~----~----~----~------~----~------~--~---
