Hi, I've used CakePHP for a few reasonably simple projects, but now I'm about to start work on a project which is a bit more complicated. This project is going to have 4 different interfaces depending on the type of user. Ie Agent, Participant, Trainer and Admin.
Previously I have used the admin feature of CakePHP, which worked great when there was the public site and the admin site. But now with 4 separate sites, but with significant amounts of shared code, I'm not sure what the best way to layout the project is? For example all of the portals will share the same model, but each portal will have varying degrees of access to the data. At work we use Java a lot, and if I was doing it in Java I'd probably use a Session Bean to handle all the shared business logic, but such concepts don't appear to directly exist in CakePHP. I see that cakephp has vendors and plugins, but I'm not sure if that is what they are meant for. Plugins don't really seem to be the right thing, because they appear to be quite independent. But vendors also seem to be for encapsulated pieces of functionality. Has anyone had any experience with multiple portals sharing the same models and views (to some extent, maybe using Elements or something)? Thanks, -Joel
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
