Hey, I can say as a personal opinion and the way i used it so far with all applications i've written (with or without ZF) , I always use two separate login screens for the front end and the back end, From several reasons, First is that extra security, Second it's easier for me to manage it later on if i need something and don't won't to mixup with both applications, So i use that as two seperate applications, The front and back of the core application.
Using the modular architecture you will be able to create as many modules as you like, And with a little of tweaking the ZF front controller and bootstrap file you will be able to separate each module into two sections for the front and back modules. Vince. On Mon, Mar 30, 2009 at 7:02 PM, Andrei Iarus <[email protected]> wrote: > Hello to everyone, > > Most big applications have a separate folder "admin area", from which the > application behaviour + other parts are managed. One needs to log in again > there (no matter whether he is already logged in in the user area). Another > possibility is to mix the admin area with the user area. > First question, what do you think about this: which is better? As advantage > for separating the areas I : > -if the admin is logged-in in the user area and forgets to log out, > then someone who will grant access to that browser, will not have acces to > the admin area > -it seems cleaner so. > > Our application will have more modules. Every module can be splitted into > user area and admin area. If the decision to create the admin module would > be taken, how would it be possible in ZF? If accesing the /admin/ module, > how is it possible to acces admin areas of other modules, something like > /admin/module1/controller1/action1/? > > Thank you very much in advance > > -- Vincent Gabriel. Lead Developer, Senior Support. Zend Certified Engineer.
