I am new to MVC programming, but think I have my head wrapped around it
at an individual application level. I am working on project that will
have multiple MVC applications (mostly CRUD applications) that need to
be wrapped into one seamless experience. Users are able to access the
individual MVC Applications; but only if they have permissions
(permissions are checked at the individual application controller
level). I would like to take a "two-tier" approach in the directory
structure (Appendix I - Directory Structure). The issue that I'm
struggling with is how to best develop a router that gets users to the
individual MVC application on a multi-level directory. I have looked at
Phalcon and YAF as our framework, but may have to develop a custom
framework due to the database servers/types the applications will
connect to. I have not found any good best practices/examples that
involve routing to multiple MVCs. I'm afraid that one router file will
be too big, but unsure of how to best handle multiple router files.
Initially we started working with Laravel, but abandoned it due to
database issues. I have explored Phalcon and YAF, but still not sure if
I want to head down that route. The current direction is developing my
own PHP framework for our needs.
Anyone have any best practices or suggestions on which direction we
should head with this type of application? I am not afraid to abandon
our current concept and venture down another path. I've spent a lot of
time trying to figure out which direction to take, but in the end, have
gotten nowhere! Need some advice!
_*Appendix*__*I - Directory Structure*_
accounting/
+-general_ledger/
+-controllers/
+-model/
+-views/
+-purchase_orders/
+-vendor_maintenance/
customer_service/
+-customer_accounts/
+-payments/
+-worker_orders/
human_resources/
+employee_checkstubs/
+reports/
+time_clock/
--
Jason Aleski / IT Specialist
