Forum: Ruby on Rails Structure for complicated controller

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
F48118fe74b0c7f6fd82a0ee422fa34e?d=identicon&s=25 snacktime (Guest)
on 2007-02-19 02:16
(Received via mailing list)
I have a fairly complicated controller and thought I'd post how I'm
structuring it in case anyone else has a better idea.  It's going to
be open source, so eventually people will be able to comment on the
design anyways.

The controller is an entry point for a service that provides a unified
api to a number of different backend services.  The controller has
very little code, and I've put most of the code in modules under
rails_root/lib.  Is there a reason to not do it this way?  One reason
I structured it this way is so the api could be used directly.  You
can run rails and offer it as an api via http post, or just use the
api directly from your code.

This topic is locked and can not be replied to.