Hey, I am always open for new ideas, this one sounds like something similar i have done just without the several bootstrap files. I use a single bootstrap file for the entire application, I am not sure if more then one is a good practice but worth a shoot. That said, I think ZF introduces some new techniques for purposes such as these. Matthew has some demo in his demo application.
What i usually do is create 3 files that i place inside a library directory with all common library classes, the first i name it MasterController.php and that class extends Zend_Controller_Action the two others are BaseFrontController.php & BaseEndController.php both extends MasterController each inherits the properties Mastercontroller has, And loads additional sections for the front & back respectivly. I am not sure if this is the *best* practice and the best way of doing this, But it works like a charm, Both performance-wise and scalability. Vince. On Wed, Apr 1, 2009 at 1:23 PM, Andrei Iarus <[email protected]> wrote: > Thank you for your answer, Vadim. > > I thought to this solution: > create in the public/ folder an admin/ folder, with an index.php in it. > This file would include an bootstrap_admin.php, instead of the bootstrap.php > file. Of course, all the admin specific part would be here loaded (in > bootstrap_admin.php), and the application areas (user&admin) would run > independently, but the files of both areas would reside in every modules > folder. This separation would be done because of performance. What do you > think about it? Does anyone here have better ideas? > > Andrei > > --- On *Mon, 3/30/09, Vadim Gabriel <[email protected]>* wrote: > > From: Vadim Gabriel <[email protected]> > Subject: Re: [fw-general] Admin module and other modules > To: [email protected] > Cc: [email protected] > Date: Monday, March 30, 2009, 10:16 PM > > > 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. > > > > > > -- Vincent Gabriel. Lead Developer, Senior Support. Zend Certified Engineer.
