The concept of nesting complete fusebox applications

[Shane Johnson]

Hey all,   I am struggling to grasp how this works.  If you have an application that runs perfectly as a standalone, and in this instance I am referring to Tom’s security manager, how do you incorporate it into another existing application seamlessly so that you call it as a native circuit like so…   http://localhost/testapps/ugc/index.cfm?fuseaction=user.home   Instead of …   http://localhost/testapps/ugc/users/index.cfm?fuseaction=main.home   Note the extra directory in there.  I am about to embark on a major rewrite so that it is just like any other circuit and with its circuit definitions moved to the root applications fbx_circuits.cfm, but I have a nagging feeling that I am missing something conceptual here that will result in my not having to do that.   The security manager, which I am calling “users” here, has its own fbx_circuits of course and it even has a nested app that in turn has its own fbx_circuits.  In fact his app has every circuit as a standalone in that they all have the core files in their respective directories.   Is what I am asking making any sense to anyone? I have a nasty habit of asking questions on this list that get few if any responses. I suspect because they are too boneheadish.   Thanks in advance for any thoughts…   Shane Johnson Macromedia Certified Coldfusion Developer www.strangetactics.com 604.999.0866   ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================