I like to put both in the same circuit. It allows me to make a circuit, admin functionality and all, in one site and drag it into another site later. I have actually done this a few times and it has worked out really well. Mind you, I define the rules for my apps pretty tightly, so parts from one tend to work very well in another.
I handle security on a fuseaction level (actually, I split out security within a fuseaction, but that is a story for another day). Hope that helps! Steve At 12:28 PM 6/18/2002 -0600, Emilio Gagliardi wrote: >Greetings Fuseboxers! > >It has been a while, but I m wading back into the thick of it. > > > >The question I d like to pose deals with the physical location of >administrative functionality. Should it be contained within the circuit >that it is designed to interact with, or whether it is best left outside >the circuit. The former is inspired by my experience with objects, in >that, all getter and setter methods are contained within the class (lets >*forget* about inheritance for now) while the latter seems to be the >favoured with fuseboxers. I like the idea of having everything that >manipulates an entity eg. a user - in one place. Now, if the >administrative functionality is distinctly separated from the circuit in >question, security becomes easier to manage, but it seems duplicated code >may result. > > > >As a restriction to your responses, I would prefer to look at solutions >based on vanilla Fusebox and not FuseQ or MVC simply because am I helping >a friend work on a PHP implementation and converting the above techniques >would just be extra over-head right now. > > > >Please feel free to point me in the direction of previous posts or extra >resources for any background reading that I should have under my belt. > > > >Example: > >A user circuit allows users to update their personal information, but not >their salary, for instance. So the user circuit contains a display file >for the form, a query to fetch their record, and an action to update any >changes. An administrator should be able to do what the user does, plus, >they should be able to edit the user s salary field. To me, it makes >sense to add that functionality into the user circuit, so I can access the >same query and action file. Breaking the admin functionality into an >Admin circuit means I now have to create a display file, a query file, and >an action file in the admin circuit. Of course, you can create a >FuseAction within the user circuit that returns a recordset, but you >still, potentially, have a form and an action file contained within the >admin circuit that almost duplicate the code within the user circuit. I >*think* I ve seen it mentioned that, separating the admin out allows you >to use the circuit where ever you need it without having to worry about >the extra functionality being bundled along with it??? Lastly, security >is allows a lurking bed fellow that I would like to deal with. In the all >inclusive instance, what would be a method to secure specific FuseActions >that will still allow the circuit to run independently of an Admin circuit. > > > > All insight and comments are welcomed. > > > >Cheers, > >_- Emilio -_ ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
