On Sat, Feb 11, 2012 at 2:07 AM, howesc <how...@umich.edu> wrote: > one option working with the framework as is: > > - make a controller called jsonrpc with 1 method > - use the first arg from the request.args to select the module to call > - create a directory in modules and put all your calls in there. > - import and invoke the modules as needed by the controller (passing in > request and whatever else is needed) > > in that case you write 1 controller and forget about it, and then create > the modules just as you were planning to make controllers.
Look interesting but that would make the service URLs a bit ugly . i would prefer each UI having its own service URL not generic single method. What i want is like this : /controllers/services/case.py /controllers/services/dashboard.py /controllers/services/result_grid.py /controllers/services/front.py /controllers/services/import_wizard.py /controllers/services/export_wizard.py ..... more each service will have 5 - 10 JSORPC method. Which is totally clean and descriptive Currently it look like this : /controllers/default.py /controllers/runonce.py /controllers/extraction.py /controllers/parser.py /controllers/case_service.py /controllers/dashboard_service.py /controllers/result_grid_service.py /controllers/front_service.py /controllers/import_wizard_service.py /controllers/export_wizard_service.py ..... more Even now it is becoming hard to manage , when its going to grow much bigger , over 20 - 50 files for web and JSONRPC - it will be a night mare. Can we have folder organization inside controllers ? If that not possible, As JSONRPC service do not interprete /after_controller/as_args can we atleast have JSONRPC and any other services to have subfolders ? This will ease a lot of pain in code management and also.
